Borrowing it
Nothing to install: this file belongs to frostyard/snosi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/frostyard/snosi/main/.agents/skills/frostyard-repo-docs/SKILL.mdgit clone --depth 1 https://github.com/frostyard/snosiWrote 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/frostyard/snosi/frostyard-repo-docs)<a href="https://agentmods.dev/skills/frostyard/snosi/frostyard-repo-docs"><img src="https://agentmods.dev/badge/skills/frostyard/snosi/frostyard-repo-docs/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/frostyard/snosi/frostyard-repo-docs"><img src="https://agentmods.dev/badge/skills/frostyard/snosi/frostyard-repo-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00119 | $0.01660 |
| Opus 5 | $0.00060 | $0.00830 |
| Sonnet 5 | $0.00024 | $0.00332 |
| Haiku 4.5 | $0.00012 | $0.00166 |
Grade A, and why
frostyard-repo-docs 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 11d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
frostyard-repo-docs — core's docs shape, in every repo
Every frostyard repo keeps one documentation tree, docs/, in the same
shape as frostyard/core's
(core ADR-0025):
| Directory | Question | Contents |
|---|---|---|
docs/adr/ |
Why did we choose this? | Repo-local ADRs — immutable once accepted; org-wide decisions go to core instead |
docs/design/ |
How does it fit together? | Living architecture docs; overview.md is the entry point |
docs/specs/ |
What exactly is the contract? | Precise interface/format definitions, changed only alongside code |
docs/plans/ |
When/in what order do we build? | Phased plans with "Done when" outcomes |
docs/README.md carries this table plus an index of every doc.
docs/org-adrs.md lists the core ADRs binding the repo, linked from the
index. There is no separate "AI docs" directory — all docs are written to
be maximally useful in an agent's context window (style rules below). This
skill descends from the retired yeti service's doc-maintainer job
(prompt).
Step 0 — Scaffold and migrate (once per repo)
If the repo lacks the shape, or still has a yeti//cairn/ tree:
- Create the four category directories and seed each with core's
canonical template (do not invent your own):
https://raw.githubusercontent.com/frostyard/core/main/docs/<category>/TEMPLATE.mdforadr,design,specs,plans. - Create
docs/README.mdmodeled onhttps://raw.githubusercontent.com/frostyard/core/main/docs/README.md: the category table, an index section per category, and the conventions block (new docs start from the category TEMPLATE; new decision → new ADR with the next number; adding a doc means indexing it). Index every pre-existingdocs/*.mdfile where it stands — do not force-move uncategorized process docs; categorize them opportunistically later. - Migrate the legacy tree with
git mv:OVERVIEW.md→docs/design/overview.md- contract/reference docs (APIs, file formats, config references) →
docs/specs/<name>.md; other subsystem docs →docs/design/<name>.md learnings/*→ fold each into the right doc now and delete it; a learning not yet foldable moves to the.memory/inbox.
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.
- 11d ago First seen · 110 lines · 119 tokens per session scan A 0086f9e1fc27
frostyard-repo-docs is a skill published in the GitHub repository frostyard/snosi (24 stars, last pushed today), licensed MIT. It adds 119 tokens to every session and 1,660 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-30.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…