The token is an access credential, not a meter, so an AI worker crawling the kit chapters fetches what it asks for. Nothing in the kit spec says the token counts fetches or expires after a set number of them. If you want to know what your worker read, ask it to list the files it pulled, or have it write a short summary per chapter after each fetch. That record lives in your worker's output, not in a dashboard on my side.
If a run goes sideways, stop it. You control the worker, so kill the process or revoke the token from your side and restart with a narrower instruction.
A tight loop:
- Give the worker a short task that names the chapters and module specs it needs.
- Have it log each URL it fetches, one line per fetch, with the file name.
- After the run, read the log and compare against the 12 modules.
- If it wandered, narrow the prompt to the exact files and run again.
What is free: the 206-page PDF, the reference codebase, the AI crawl token and prompt. What is paid: the 3 week program, the $19 Prigmar prompt set, and community tools when you choose them. I do not have a published fetch limit for the token yet. When I do, it goes on the site.
Keep the loop small. Check the log. Move on.
Mouldi