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 safe-data-exportgit 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/safe-data-export)<a href="https://agentmods.dev/skills/iamakbarsha1/whetstone/safe-data-export"><img src="https://agentmods.dev/badge/skills/iamakbarsha1/whetstone/safe-data-export/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/safe-data-export"><img src="https://agentmods.dev/badge/skills/iamakbarsha1/whetstone/safe-data-export.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.00094 | $0.01231 |
| Opus 5.5 | $0.00038 | $0.00492 |
| Sonnet 5.5 | $0.00019 | $0.00246 |
| Haiku 4.5 | $0.00009 | $0.00123 |
Grade A, and why
safe-data-export 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 11d 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.
- 11d ago Changed · +18 lines 75eb72a3a735
- 2mo ago First seen · 85 lines · 94 tokens per session scan A 4f00e2c40a3a
safe-data-export is a skill published in the GitHub repository iamakbarsha1/whetstone (4 stars, last pushed 6d ago), licensed CC-BY-4.0. It adds 94 tokens to every session and 1,231 once invoked, about $0.0004 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-commit
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes…
guardian
Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy; the ship recipe also executes PR delivery (create, CI watch, merge, cleanup) with Ask First on merge. Use when PR preparation, commit strategy, or gated PR delivery is needed.
trail
Investigating git history, analyzing regression root causes, and performing code archaeology. Time-travels through commits to uncover truth. Use for git history investigation.
pr-authoring
Playbook for deployment-aware pull requests — the 11-section format that turns a PR into a reviewable contract; why, decision requested, change map, review order, evidence, verification, risk, rollback. Used for the Define→build handoff and any PR a great-pm-driven project opens.
pr-review
Playbook for reviewing pull requests — verdict format, verification-not-trust, severity-ranked findings with concrete fixes, risk acceptance on the record. The reviewer-side counterpart of pr-authoring.
kumihimo-iteration
Run ONE iteration of the Kumihimo build loop — take the next item off the queue, ground it against PLAN.md, build it, verify it, document it, commit it. Use when Thomas invokes /kumihimo-iteration (often wrapped in /loop for unattended runs) or asks for another build pass on Kumihimo. Covers the queue, verification…