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 vidhunnan/agentic-skills --skill repo-setupgit clone --depth 1 https://github.com/vidhunnan/agentic-skillsWrote 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/vidhunnan/agentic-skills/repo-setup)<a href="https://agentmods.dev/skills/vidhunnan/agentic-skills/repo-setup"><img src="https://agentmods.dev/badge/skills/vidhunnan/agentic-skills/repo-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vidhunnan/agentic-skills/repo-setup"><img src="https://agentmods.dev/badge/skills/vidhunnan/agentic-skills/repo-setup.svg" alt="Reviewed on agentmods" width="80" 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.00129 | $0.05921 |
| Opus 5 | $0.00064 | $0.02960 |
| Sonnet 5 | $0.00026 | $0.01184 |
| Haiku 4.5 | $0.00013 | $0.00592 |
Grade A, and why
repo-setup 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
repo-setup
Builds a project's context stack: the documentation tiers that let an agent with no memory be briefed on a project. Each tier answers one question a human teammate would ask — what are we trying to build, what are we still deciding, why did we choose that, what actually shipped, where did we leave off — and each one declares how much an agent should trust it.
The anchor rule the whole stack exists to enforce is done vs. explored: changelog/ is what shipped (truth, past tense, generated from git); everything under docs/ is what we thought (hypothesis, hand-written, disposable). Mix them and you have handed a teammate contradictory instructions — a human pushes back, an agent just agrees, confidently, in both directions.
Two principles govern every step:
- Detect, map, confirm — never impose. If the repo already calls it
docs/adr/, then the decisions tier isdocs/adr/. Canon fills gaps; it does not rename anyone's repo. - Additive only. Never move, rename, delete, or overwrite. Every write is a file that did not exist. If the right answer requires moving files, say so and let the human do it.
The canon
Used only to fill gaps — an existing path always wins (see Step 1).
| Tier | Canonical path | Question it answers | Status |
|---|---|---|---|
| Concepts | docs/concepts/ |
What are we even trying to build? | hypothesis — future tense, disposable |
| PRDs | docs/prds/ |
What are we still deciding? | proposal — a concept worth building |
| Decisions | docs/decisions/ |
Why did we choose that? | truth — past tense, append-only |
| Handoffs | docs/handoffs/ |
Where did we leave off? | snapshot — the latest one wins |
| Changelog | changelog/ |
What actually shipped? | TRUTH — generated from git |
| Phases (opt-in) | docs/phases/ |
What's the plan to build it? | plan — gated by an exit checklist |
changelog/ sits outside docs/ deliberately: docs/ is hand-written hypothesis, changelog/ is generated truth. The folder layout is the done-vs-explored rule.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 279 lines · 129 tokens per session scan A 8d6e400caba4
repo-setup is a skill published in the GitHub repository vidhunnan/agentic-skills (2 stars, last pushed 6d ago), licensed MIT. It adds 129 tokens to every session and 5,921 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…