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 agentmods add skills/yarlson/yarstack/repo-context-documentnpx skills add yarlson/yarstack --skill repo-context-documentgit clone --depth 1 https://github.com/yarlson/yarstackWrote 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/yarlson/yarstack/repo-context-document)<a href="https://agentmods.dev/skills/yarlson/yarstack/repo-context-document"><img src="https://agentmods.dev/badge/skills/yarlson/yarstack/repo-context-document.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 | $0.00040 | $0.00357 |
| Opus 5 | $0.00020 | $0.00179 |
| Sonnet 5 | $0.00008 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
repo-context-document 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 4d 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
Repository Context Documentation
Own the information architecture and current-state content under an adopted docs/context/ system.
Workflow
- Confirm requested topics, audience, repository adoption of
docs/context/, dirty-worktree preservation, and authority for moves or removals. - Read all existing context files and the minimum repository evidence needed to verify their claims.
- Classify units by entrypoints, runtime roles, deployment, consumers, state, and contracts rather than directory names.
- Create or update only justified topic files before updating the terse context index.
- Remove stale claims and duplicate facts; merge or remove files only when authorized.
- Verify every edited claim against current implementation.
- Use
text-improveon edited prose without weakening architectural precision or established terminology.
Write only under docs/context/. Use docs-drift-review for incidental change-caused drift, docs-review for general documentation, and critical-journey-document for actor-goal journeys. Link to canonical plans, specifications, runbooks, guides, and API references instead of duplicating them.
Record implemented responsibilities, ownership, runtime roles, contracts, state, invariants, dependency direction, and concise system flows. Exclude history, progress, raw file inventories, speculative design, TODO lists, duplicated instructions, and sensitive values.
Do not impose docs/context/ on a repository that has not adopted it without an explicit request.
Finish with the context files created, updated, consolidated, or removed and the evidence used.
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.
- 4d ago First seen · 27 lines · 40 tokens per session scan A 579baf4ac366
repo-context-document is a skill published in the GitHub repository yarlson/yarstack (3 stars, last pushed 7d ago), licensed MIT. It adds 40 tokens to every session and 357 once invoked, about $0.0002 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
opensrc
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for"…
release-cli
Release a new version of the tokenmaxxing CLI to npm. Use when explicitly asked to release or publish @851-labs/tokenmaxxing, including checking main, bumping apps/cli/package.json, updating CHANGELOG.md, committing, tagging cli-vX.Y.Z, pushing, monitoring generated native package publishing, and smoke testing the…
audit-plan-implementation
Independently audit a task attempt or completed run against a frozen plan, checking ownership, evidence, acceptance, and final readiness.
agent-first-planning
Create or revise production-ready SDD plans for agent execution, including clarification, specification, freeze inputs, ownership, budgets, and evidence contracts.
ship-mobile-app
Build, change, debug, and prepare production mobile apps across domain meaning, local and server state, lifecycle, platform, and release boundaries. Use for non-trivial Flutter, React Native, iOS, or Android work involving persistence, sync, auth, offline behavior, notifications, permissions, native integrations…
verify-regression-tests
Verify that a regression test actually detects the defect it claims to guard against. Use after adding or reviewing a bug-fix guard, reproducing the original failure after a fix, or investigating a suspiciously green regression test. Do not use for general TDD, broad test-suite audits, mutation-score optimization…