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 skills add kpab/claude-fable-5-skills --skill no-gold-platinggit clone --depth 1 https://github.com/kpab/claude-fable-5-skillsWrote 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/kpab/claude-fable-5-skills/no-gold-plating)<a href="https://agentmods.dev/skills/kpab/claude-fable-5-skills/no-gold-plating"><img src="https://agentmods.dev/badge/skills/kpab/claude-fable-5-skills/no-gold-plating/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/kpab/claude-fable-5-skills/no-gold-plating"><img src="https://agentmods.dev/badge/skills/kpab/claude-fable-5-skills/no-gold-plating.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.00100 | $0.00612 |
| Opus 5 | $0.00050 | $0.00306 |
| Sonnet 5 | $0.00020 | $0.00122 |
| Haiku 4.5 | $0.00010 | $0.00061 |
Grade A, and why
no-gold-plating 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 8d 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
No Gold-Plating
At higher effort, Fable 5's thoroughness can spill over into the diff: speculative abstractions, defensive checks for impossible states, cleanup nobody requested. Fable 5.1 adds a variant of its own on open-ended features: fixing nearby code, extending behavior the task never mentioned, and committing more test files than the change warrants. Each of these enlarges review surface and risk. The discipline:
Rules
- The diff should map one-to-one to the request. A bug fix touches the bug; it does not reorganize the neighborhood.
- No helpers, layers, or abstractions for a single call site. Inline it.
- Do not design for requirements that don't exist yet. The simplest correct implementation wins; generality is a cost paid today for a benefit that may never arrive.
- Validate only at system boundaries — user input, external APIs, file contents. Inside the system, trust the framework and your own invariants; do not add error handling for states that cannot occur.
- Prefer changing code over compatibility shims, flags, or deprecation layers, unless the code is a published interface someone else depends on.
- A pre-existing bug, performance issue, or unmentioned behavior you run into stays untouched unless the requested behavior cannot work without fixing it. Report it as a follow-up in your summary.
- When the task is ambiguous, implement the reading its wording and the surrounding code most directly support, state that assumption in your summary, and do not build for the other readings as well.
- Commit tests only where the task asks for them or the repository already keeps tests for this kind of change. Size them like the neighboring test files — roughly one focused test per stated behavior — and never promote scratch checks into permanent test files. Verify however you like meanwhile; scratch scripts need not survive.
- If you notice genuinely valuable adjacent work, note it in one sentence at the end. Do not do it.
This is about extras only: every behavior the task does ask for gets implemented completely.
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.
- 8d ago Changed · +6 lines · +22 tokens per session 93655d3d9a38
- 12d ago First seen · 26 lines · 78 tokens per session scan A 2ac5ea6cf646
no-gold-plating is a skill published in the GitHub repository kpab/claude-fable-5-skills (17 stars, last pushed 10d ago), licensed MIT. It adds 100 tokens to every session and 612 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
ddd:software-architecture
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
thermo-nuclear-code-quality-review
A strict code-quality review workflow for examining changes in a branch, commit, or pull request. A pull request is a proposed change for review before it is merged into the main codebase.
code-review
Review code for bugs, security vulnerabilities, performance issues, and maintainability. Trigger with "review this code", "check this PR", "look at this diff", "is this code safe?", or when the user shares code and asks for feedback.
007
Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
cookbook-audit
Audit an Anthropic Cookbook notebook based on a rubric. Use whenever a notebook review or audit is requested.