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 iamakbarsha1/whetstone --skill verify-absence-claimsgit clone --depth 1 https://github.com/iamakbarsha1/whetstoneWrote 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/iamakbarsha1/whetstone/verify-absence-claims)<a href="https://agentmods.dev/skills/iamakbarsha1/whetstone/verify-absence-claims"><img src="https://agentmods.dev/badge/skills/iamakbarsha1/whetstone/verify-absence-claims/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/iamakbarsha1/whetstone/verify-absence-claims"><img src="https://agentmods.dev/badge/skills/iamakbarsha1/whetstone/verify-absence-claims.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.00220 | $0.02717 |
| Opus 5.5 | $0.00088 | $0.01087 |
| Sonnet 5.5 | $0.00044 | $0.00543 |
| Haiku 4.5 | $0.00022 | $0.00272 |
Grade A, and why
verify-absence-claims 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 3d 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.
The source is not reproduced here
Licensed CC-BY-4.0
The repository is licensed CC-BY-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 3d ago Changed · +78 lines · +75 tokens per session b8ea4663132b
- 9d ago Changed · +41 lines · +13 tokens per session c2f13cea6f6b
- 10d ago Changed · +5 lines aef39f3ba6ac
- 1mo ago First seen · 77 lines · 132 tokens per session scan A 422a1f166355
verify-absence-claims is a skill published in the GitHub repository iamakbarsha1/whetstone (4 stars, last pushed 3d ago), licensed CC-BY-4.0. It adds 220 tokens to every session and 2,717 once invoked, about $0.0009 per session on Opus 5.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
lean-audit
Whole-repo audit for over-engineering. Like lean-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat"…
code-review
Reviews code for bugs, security issues, and best practices.
bug-reproducer
Find likely software bugs in a codebase, rank concrete bug candidates, and prove or reject them with focused regression tests before proposing a fix. Also turn bug reports, stack traces, screenshots, failing behavior, support tickets, and regressions into minimal reproducible cases with red-to-green evidence. Use when…
root-cause-delivery
Use for a reported bug, regression, crash, failed workflow, or substantive code change that must reach a verified candidate rather than a local patch. Map the affected layer, freeze a bounded plan, require incident reproduction red-to-green or planned-change contract proof, force re-triage after two failed attempts…
reverse-engineer-anything
Reverse-engineer binaries, firmware, and web apps with REA AgentEnv / Rekayasa balik biner, firmware, dan web apps dengan REA AgentEnv.
error-resilience-expert
Expert guide for error handling patterns, resilience engineering, retry strategies, circuit breakers, and graceful degradation across React, Next.js, and Node.js / Panduan ahli pola penanganan error, rekayasa ketahanan, strategi retry, circuit breaker, dan degradasi anggun di React, Next.js, dan Node.js.