Borrowing it
Nothing to install: this file belongs to agentculture/reachy-mini-mcp. 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/agentculture/reachy-mini-mcp/main/.claude/skills/doc-test-alignment/SKILL.mdgit clone --depth 1 https://github.com/agentculture/reachy-mini-mcpWrote 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/agentculture/reachy-mini-mcp/doc-test-alignment)<a href="https://agentmods.dev/skills/agentculture/reachy-mini-mcp/doc-test-alignment"><img src="https://agentmods.dev/badge/skills/agentculture/reachy-mini-mcp/doc-test-alignment/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/agentculture/reachy-mini-mcp/doc-test-alignment"><img src="https://agentmods.dev/badge/skills/agentculture/reachy-mini-mcp/doc-test-alignment.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.00101 | $0.00631 |
| Opus 5 | $0.00051 | $0.00316 |
| Sonnet 5 | $0.00020 | $0.00126 |
| Haiku 4.5 | $0.00010 | $0.00063 |
Grade A, and why
doc-test-alignment 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 10d 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.
Copies of this mod
5 near-identical copies found in the catalogue:
- doc-test-alignment — 100% identical, 0 lines differ
- doc-test-alignment — 100% identical, 0 lines differ
- doc-test-alignment — 100% identical, 0 lines differ
- doc-test-alignment — 100% identical, 0 lines differ
- doc-test-alignment — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-test-alignment (stub)
This skill is a stub. The real workflow is intentionally not yet implemented —
the file exists so that steward verify can find it and so contributors who
land here know it is on the roadmap, not forgotten.
How to run
scripts/check.sh is the entry point. Today it prints a not-yet-implemented
notice and exits non-zero. When the workflow lands, the script will gate
PR-readiness on the alignment contract below; until then, treat any green
exit code from this script as a bug.
What it will check
The skill is the contract for four narrow alignments. README.md command
examples must still execute against the current checkout and produce output
that matches the surrounding prose. The "build/test/publish" command lines in
CLAUDE.md must do the same. For each .claude/skills/<name>/, the SKILL.md
description frontmatter must agree with what the scripts under
scripts/ actually do — surfacing disagreements (e.g. SKILL.md claims the
skill bumps versions but scripts/ has no bump script). And for each test,
the test name should still describe the assertions the test makes — flagging
drift where the name advertises a feature the assertions no longer touch.
Why it ships as a stub
Each of those four checks is independently non-trivial. Shipping a partial
implementation would either silently pass when it shouldn't, or false-positive
on intentional doc-vs-code differences. The right path is to land the checks
one at a time, with their own tests, behind a
steward verify --check doc-test-alignment flag. The parent verbs (verify,
doctor) are named in the "Roadmap" section of CLAUDE.md; the broader
sibling-pattern contract lives in docs/sibling-pattern.md.
What this stub guarantees today
- The skill directory exists, so
steward verify's skills-convention check finds the standard layout (SKILL.md +scripts/with an entry-point). scripts/check.shis the entry-point script, satisfying the steward skills convention requirement that every skill ships an executable script.- This
SKILL.mdis the contract for what the skill will do — when the implementation lands, it must satisfy this description or the description must move first.
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.
- 10d ago First seen · 57 lines · 101 tokens per session scan A 30b43ee97999
doc-test-alignment is a skill published in the GitHub repository agentculture/reachy-mini-mcp (32 stars, last pushed 1mo ago), licensed MIT. It adds 101 tokens to every session and 631 once invoked, about $0.0005 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.