Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/shawnclybor/clybor-claude-toolingnpx agentmods add skills/shawnclybor/clybor-claude-tooling/yellow-sheet-corpusWrote 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/shawnclybor/clybor-claude-tooling/yellow-sheet-corpus)<a href="https://agentmods.dev/skills/shawnclybor/clybor-claude-tooling/yellow-sheet-corpus"><img src="https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/yellow-sheet-corpus/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/shawnclybor/clybor-claude-tooling/yellow-sheet-corpus"><img src="https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/yellow-sheet-corpus.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.00173 | $0.07327 |
| Opus 5.5 | $0.00069 | $0.02931 |
| Sonnet 5.5 | $0.00035 | $0.01465 |
| Haiku 4.5 | $0.00017 | $0.00733 |
Grade A, and why
yellow-sheet-corpus 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 1mo 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 — 472 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Yellow Sheet — the end-to-end run
Read mem:yellow_sheet/core first if you have not. This skill is the operational half: how to
point the chain at a matter, what to run, and how to read what comes back.
The one command
cd .claude/PRPs/build-a-yellow-sheet/case-folder
python3 tests/run_corpus.py # every matter the corpus declares
python3 tests/run_corpus.py matter-r matter-s # named matters only
python3 tests/run_corpus.py --summary # re-print the table, run nothing
python3 tests/run_corpus.py --intake-only # check every manifest against its folder, run nothing
Fresh case folder per matter under ~/{{CLIENT}}-cases/_corpus-<matter>, extract_sources over the
packet PDFs, then yellow-sheet.sh. Nothing hand-staged and nothing seeded by
import_yellow_sheet — a record seeded from the firm's own sheet cannot test whether we can
produce one. Logs land in ~/{{CLIENT}}-cases/_corpus-logs/.
Its exit code is a verdict, not a status.
| exit | means |
|---|---|
| 0 | complete — every matter ran and no document is refused as UNREAD |
| 1 | INCOMPLETE — the chain ran, and one or more documents were refused as UNREAD with their figures still on the page |
| 2 | an intake violation, or a matter that could not run. Nothing was measured |
⚠ Exit 1 is the normal state today and it is not a failure of the run. It is the open list.
⛔ Before you write what a document says
Run python3 investigate.py <sources/<key>.txt | case-dir> <claim> and cite the file:line it
returns. If it prints NOT IN TEXT, write exactly that: it is a fact about our extraction, not
about the page, so render the page before saying the document lacks the figure. A line marked
weak matched only a bare integer (a date, a count, a box number) and binds to no column.
.claude/hooks/check-document-claims.py denies an uncited absolute claim about a named document in
this skill, the yellow-sheet memories and PRP prose; when you repeat someone else's claim, quote it
rather than restate it.
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.
- 1mo ago First seen · 472 lines · 173 tokens per session scan A 9c7fdf33b253
yellow-sheet-corpus is a skill published in the GitHub repository shawnclybor/clybor-claude-tooling (6 stars, last pushed 8d ago), licensed MIT. It adds 173 tokens to every session and 7,327 once invoked, about $0.0007 per session on Opus 5.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-09-05.
Other skills, from other repositories
docx
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when…
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and…
verify
Verify-before-done — exercise the current change end-to-end against its acceptance criteria (the SDD plan's, or the ticket's) and report a per-criterion PASS/FAIL verdict, then record the outcome to memory. This is the concrete action that satisfies moflo's verify-before-done gate (gates.verifybeforedone / /flo -v /…
api-test
Run API integration tests against the running backend, verify endpoints return expected responses and status codes. Use after deploying a preview or starting the dev server.
undo
Revert recent PBR-generated commits by phase/plan, safely using git revert.
api-test
Run API integration tests against the running backend, verify endpoints return expected responses and status codes. Use after deploying a preview or starting the dev server.