Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add CoriChui/yolo --skill yolo-intakegit clone --depth 1 https://github.com/CoriChui/yoloWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/corichui/yolo/yolo-intake)<a href="https://agentmods.dev/skills/corichui/yolo/yolo-intake"><img src="https://agentmods.dev/badge/skills/corichui/yolo/yolo-intake.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00118 | $0.00536 |
| Opus 5 | $0.00059 | $0.00268 |
| Sonnet 5 | $0.00024 | $0.00107 |
| Haiku 4.5 | $0.00012 | $0.00054 |
Grade A, and why
yolo-intake scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
yolo-intake
Intake is context enrichment, not fetching. yolo never fetches, imports, or copies external
material. It simply references a selected folder — by default the project's docs/ — and
reads from it to enrich a feature's context. Populating that folder (pulling in a Figma, a spec,
a URL, a DB schema) is the job of the docs engine or another connector, done separately and
outside yolo. yolo only reads what's already there.
The selected folder
- The intake folder is
intake.folderinworkspace/config.yaml— defaultdocs/. Point it at a different folder only if your reference material lives elsewhere. - Whatever is in that folder is YOLO's context shelf. YOLO reads it; it never puts things there.
Procedure
- Resolve the intake folder from
workspace/config.yaml(intake.folder, defaultdocs/). - Read the relevant material from it for the feature — search the docs engine first, then read the specific files. Never fetch a live source. If needed context isn't in the folder, say so (a connector / docs-engine step must add it first) rather than fetching it yourself.
- A feature brief points at the specific files it relies on via its
intake_refslist — paths under the intake folder (e.g.docs/explanation/payments-spec.md).
Constraints
- Never fetch or import. No WebFetch, no MCP fetch, no CLI pull, no copying into the workspace. Intake is strictly read-only over the selected folder.
- One folder, one source of context — don't scatter reference material across the workspace.
- If required context is missing from the folder, surface the gap; adding it is a connector / docs-engine concern, outside yolo.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 33 lines · 118 tokens per session scan A f83717b663da
yolo-intake is a skill published in the GitHub repository CoriChui/yolo (9 stars, last pushed 2mo ago), licensed MIT. It adds 118 tokens to every session and 536 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
capture-milestone-principle-updates
Distill reusable answering principles from a just-finished milestone's recorded decisions into the project-wide principle store.
context
Context lifecycle as thin seams over native primitives (/foundry:context ). WRAP of the retired context-lifecycle skills — additive over native /compact, --resume, /rewind, and the context sensor; never reinvents transcript replay. Trigger to snapshot/resume a session's distilled arc-state or check context budget.
learn-distill
Cluster session-learning records into HBK/memory/skill candidates (/foundry:learn-distill), on a native-scheduled cadence. The distill consumer (token-overlap clustering, deterministic) is CUSTOM; the CADENCE is a WRAP over native ScheduleWakeup/CronCreate. Trigger on the scheduled tick or when the operator asks for a…
grimoire
Use when the user says 'update context', 'update claude', 'save library', or after significant project changes.
ln-31-performance-optimizer
Profiles and improves a measured latency, throughput, CPU, memory, or I/O problem. Not for speculative tuning or cosmetic refactoring.
ralph-memory
Manage Al semantic memory entries — list, query, and clear lessons learned across loop iterations.