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/melodic-software/claude-code-plugins/reason-dont-recitenpx skills add melodic-software/claude-code-plugins --skill reason-dont-recitegit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWrote 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/melodic-software/claude-code-plugins/reason-dont-recite)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/reason-dont-recite"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/reason-dont-recite.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.00183 | $0.01320 |
| Opus 5 | $0.00092 | $0.00660 |
| Sonnet 5 | $0.00037 | $0.00264 |
| Haiku 4.5 | $0.00018 | $0.00132 |
Grade A, and why
reason-dont-recite 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 yesterday.
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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reason, don't recite
A drift corrector for incumbency discipline. The method, re-anchor, audit
the work in flight, correct forward, report, and the tone that firing this
is not an accusation, lives in
${CLAUDE_PLUGIN_ROOT}/context/re-anchor-audit-correct.md.
Read it; this file adds only what is specific to interrogating inherited
content.
The discipline this re-anchors
Inherited content, a repo's docs, conventions, structure, processes, is
evidence of what is, never a self-justifying argument for what should
be. Resolve the source of truth per the method doc's ladder: if the
consuming project states an incumbency / first-principles rule in its own
CLAUDE.md / .claude/rules/, re-anchor THAT. Otherwise re-anchor this
portable baseline:
- Precedent describes, it does not justify. Existing structure, coupling, "how it's always been done", and "I don't know why, it just is" describe the current state; none is an argument that the state is correct.
- Descriptive-only support earns a challenge. A rule, boundary, or process whose only backing is that it already exists gets re-derived from first principles. State the actual purpose, then test whether the incumbent form serves it, not obeyed on sight.
- A live rationale is different from inertia. A convention someone can justify on its merits is followed; one coasting on incumbency is interrogated. Separate the two before acting.
- Absence today is not out of scope. Do not dismiss a concern merely because the thing it depends on does not exist yet; judge it on its merits.
This is a distinct axis from /discipline:do-your-research. That skill
acquires external evidence you LACK; this one questions internal evidence
you INHERITED and took on faith. Firing it is a re-anchor, not an
accusation, a gentle "should we actually be doing it this way" is a
first-class use, and the audit may find every inherited choice is well
justified.
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.
- yesterday First seen · 103 lines · 183 tokens per session scan A 7d19e7948054
reason-dont-recite is a skill published in the GitHub repository melodic-software/claude-code-plugins (14 stars, last pushed yesterday), licensed MIT. It adds 183 tokens to every session and 1,320 once invoked, about $0.0009 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-09-03.
Other skills, from other repositories
phpunit-migration-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
structuring-documentation
Use when writing, editing, auditing, splitting, or measuring Markdown documentation surfaces — README.md, AGENTS.md, CLAUDE.md, and docs/ siblings. Triggers include "is this doc too long", "split this README", "measure the docs", "where does this documentation belong", "audit the documentation", and any request to…
phpunit-unit-test-writing
Use this skill when the user asks to write, generate, create, or add PHPUnit unit tests for a Shopware 6 source class — phrases like "write unit tests for X", "generate tests for ClassName", "create PHPUnit tests", "add test coverage", "test this class", "cover this with tests", "I need tests for", "unit test this"…
phpunit-migration-test-generation
Use this skill when the user asks to generate, write, or create migration tests for a Shopware 6 migration class — phrases like "generate migration tests", "write a migration test", "create migration test", "test this migration", "test Migration1234Foo". Analyzes the source migration's SQL operations to pick an…
phpunit-test-reconciling
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
release-info-writing
Use this skill when the user is completing features, deprecations, or breaking changes in the Shopware core repository that affect external developers, or when they ask to write release info, upgrade entries, release notes, release documentation, or changelog entries — phrases like "write a release info entry for my…