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 khasky/awesome-agent-skills --skill awesome-claims-auditgit clone --depth 1 https://github.com/khasky/awesome-agent-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/khasky/awesome-agent-skills/awesome-claims-audit)<a href="https://agentmods.dev/skills/khasky/awesome-agent-skills/awesome-claims-audit"><img src="https://agentmods.dev/badge/skills/khasky/awesome-agent-skills/awesome-claims-audit/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/khasky/awesome-agent-skills/awesome-claims-audit"><img src="https://agentmods.dev/badge/skills/khasky/awesome-agent-skills/awesome-claims-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00122 | $0.04434 |
| Opus 5 | $0.00061 | $0.02217 |
| Sonnet 5 | $0.00024 | $0.00887 |
| Haiku 4.5 | $0.00012 | $0.00443 |
Grade A, and why
awesome-claims-audit 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Public Claims Audit
A claim is any public sentence a reader could disprove: a permission list, a number, a quoted UI label, a copy-pasteable command, a guarantee. The code that decides it lives somewhere else — a constant, a manifest, a catalog, a route table, a locale file — and nothing links the two. A rename on one side leaves a false statement on the other, and every test stays green.
The claims that rot are not the vague ones. They are the specific, checkable ones a reader was invited to verify.
Two phases, separate on purpose: report everything first, fix second. A fix applied mid-audit changes the surface you are still reading.
Reference files (load the one you need, don't inline both):
references/claim-source-map.md— the map from each class of claim to the one file that settles it: how to build it, the template, and the resolution traps that cost the most time.references/checker-recipes.md— the four mechanical check kinds, the config schema the scripts read, and the mutation discipline that proves a check can fail.
Scripts (Node ≥18, no dependencies):
-
scripts/check-claims.mjs— runs the mechanical checks from a config you write for the product. -
scripts/prove-checks.mjs— breaks one claim at a time and asserts the owning check names it. -
scripts/map-coverage.mjs— cross-checks the claim-source map against the config, both directions. -
scripts/stage-json-keys.mjs— stages only named JSON keys when the file also carries someone else's unfinished work. -
Other runtimes — the runner is Node because that is what most public-facing repos already have. The four check kinds are ~40 lines in Python, Ruby, or Go; what matters is the discipline (fail loud when a parse stops matching, one line per check, a mutation that proves the check fires), not the language. If the project has no Node toolchain, port the config to its own test runner and say so in the report.
What ships with it
6 files 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 Changed 3c9075273517
- 6d ago Changed · +15 lines · -90 tokens per session c2211dad9d7a
- 12d ago First seen · 328 lines · 212 tokens per session scan A d46d83402c7a
awesome-claims-audit is a skill published in the GitHub repository khasky/awesome-agent-skills (8 stars, last pushed 2d ago), licensed MIT. It adds 122 tokens to every session and 4,434 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-08-31.
Other skills, from other repositories
code-review-and-quality
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
code-simplification
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
chinese-code-review
A Chinese-language code-review communication guide with templates and severity levels for review comments.
receiving-code-review
A guide for handling code-review feedback carefully. Code review is the process of checking proposed changes before they are accepted into a project.
requesting-code-review
A code-review procedure for checking completed work against its requirements before it spreads or is merged. A code reviewer is a person or agent who looks for defects and missing parts.