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 iliaal/whetstone --skill reflectgit clone --depth 1 https://github.com/iliaal/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/iliaal/whetstone/reflect)<a href="https://agentmods.dev/skills/iliaal/whetstone/reflect"><img src="https://agentmods.dev/badge/skills/iliaal/whetstone/reflect/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/iliaal/whetstone/reflect"><img src="https://agentmods.dev/badge/skills/iliaal/whetstone/reflect.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.00045 | $0.00577 |
| Opus 5.5 | $0.00018 | $0.00231 |
| Sonnet 5.5 | $0.00009 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
reflect 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 1mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reflect
Success Criteria
- Every mistake/friction point cites the specific moment and its impact
- Improvements are actionable, prioritized, and <= 10 items
- Each skill audit proposes measurable changes (not vague suggestions)
- User is asked which items to persist to memory
Process
1. Session Review
Scan the full conversation. For each finding, cite the specific exchange (quote or paraphrase) and its impact.
| Category | Signal |
|---|---|
| Mistakes | Wrong outputs, incorrect assumptions, hallucinated facts |
| Friction | Repeated clarifications, verbose responses, misread intent |
| Wasted effort | Work discarded, wrong approaches tried first |
| Wins | Approaches worth repeating, smooth interactions |
Skip one-time typos, external tool failures, and issues outside agent control.
2. Improvements
Numbered list of concrete improvements, ranked by impact. Each item: one sentence, imperative, actionable. Cap at 10.
Ask: "Which of these should I remember for future chats?"
Save approved items to memory files via the auto memory system.
3. Skill Audit (if skills were used)
For each skill invoked during the session:
A. Self-check gate — If the skill lacks success criteria + verification loop:
- Add
## Success Criteriaat top (3-5 measurable checks) - Add
## Self-Checkat bottom: "Verify all success criteria are met before presenting output. If not, iterate (max 5 times)."
B. Token efficiency — Flag: redundant phrasing, mergeable sections, oversized examples, "Claude already knows this" content, inert frontmatter metadata.
C. Other — Missing edge cases, vague directives (rewrite as measurable criteria or remove), naked negations (add "do Y instead" or remove).
Present proposed changes as diffs. Ask: "Apply these? (all / pick / skip)"
4. Pattern Detection
If 2+ similar tasks appear that no existing skill covers, suggest a new skill (1-2 sentence description). Create only after confirmation.
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.
- 1mo ago First seen · 68 lines · 45 tokens per session scan A deec149fff73
reflect is a skill published in the GitHub repository iliaal/whetstone (35 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 577 once invoked, about $0.0002 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-30.
Other skills, from other repositories
experiment-review
Analyze A/B tests and experiments with statistical rigor, assess significance, perform segment analysis, and produce a clear ship/kill/extend recommendation.
metrics-check
Review product metrics, identify trends and anomalies, connect movements to OKRs and recent changes, and produce actionable recommendations.
refine-spec
Review a PRD or spec for completeness, ambiguity, edge cases, and acceptance criteria quality. Present structured findings by severity and offer to fix issues directly.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…
spike-consumer-baseline
OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow by reading a file directly, with NO Skill-tool call. Use only when explicitly invoked by the spike harness with a TRIALID and data path.