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/mind-your-maximsnpx skills add melodic-software/claude-code-plugins --skill mind-your-maximsgit 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/mind-your-maxims)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/mind-your-maxims"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/mind-your-maxims.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.00115 | $0.01411 |
| Opus 5 | $0.00057 | $0.00705 |
| Sonnet 5 | $0.00023 | $0.00282 |
| Haiku 4.5 | $0.00012 | $0.00141 |
Grade A, and why
mind-your-maxims 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mind your maxims
A drift corrector for cooperative-communication 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 communication discipline.
The discipline this re-anchors
Cooperative communication: give the reader what they need. No less, no
more. Relevantly, clearly, and with your uncertainty and limits disclosed.
This discipline rests on maxims their primary sources own; this skill
points at them and does not restate them (it dogfoods
/discipline:point-dont-copy, a paraphrase of the maxims here would be a
second copy that drifts):
- Grice's Cooperative Principle and its four maxims. Quantity, Quality, Relation, Manner. In Grice, "Logic and Conversation" and Cooperative principle.
- The AI-augmented maxims for human-AI dialogue. Transparency and Benevolence. In Miehling et al., "Language Models in Dialogue: Conversational Maxims for Human-AI Interactions" (arXiv:2403.15115).
Resolve the source of truth per the method doc's ladder: if the consuming
project declares a communication or writing-quality convention in its own
CLAUDE.md / .claude/rules/, re-anchor THAT as well and audit against it.
The rubric this skill audits
Its own delta, the four axes this corrector owns, mapped onto the pointed-to maxims:
- Quantity, both directions. Under-informing is a finding: an asked-for detail, a load-bearing caveat, or a necessary step omitted. Over-informing is a finding too: padding, restatement, and detail the reader did not need. Both fail the reader.
- Relation. Answer the question actually asked. An adjacent answer to a question the reader did not ask, a tangent, or a buried lede (the answer present but hidden below setup) fails relevance even when technically correct.
- Manner. Unambiguous references (no pronoun or "it" the reader must resolve), ordered structure, and plain clarity over cleverness or needless jargon.
- Transparency. Disclose the boundaries: flag genuine uncertainty rather than asserting through it, and state the edges of your knowledge or capability rather than letting the reader assume completeness.
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 · 113 lines · 115 tokens per session scan A ac370cb8d9b7
mind-your-maxims is a skill published in the GitHub repository melodic-software/claude-code-plugins (14 stars, last pushed yesterday), licensed MIT. It adds 115 tokens to every session and 1,411 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-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-integration-test-generation
Use this skill when the user asks to generate, write, or create integration tests for a Shopware 6 source class whose contract requires wired-up code — phrases like "generate integration tests for X", "write an integration test for this controller", "test this indexer", "create an integration test for the message…
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.