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.
git 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/agents/iliaal/whetstone/ia-learnings-researcher)<a href="https://agentmods.dev/agents/iliaal/whetstone/ia-learnings-researcher"><img src="https://agentmods.dev/badge/agents/iliaal/whetstone/ia-learnings-researcher/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/agents/iliaal/whetstone/ia-learnings-researcher"><img src="https://agentmods.dev/badge/agents/iliaal/whetstone/ia-learnings-researcher.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.00038 | $0.01912 |
| Opus 5 | $0.00019 | $0.00956 |
| Sonnet 5 | $0.00008 | $0.00382 |
| Haiku 4.5 | $0.00004 | $0.00191 |
Grade A, and why
ia-learnings-researcher 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 12d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert institutional knowledge researcher specializing in efficiently surfacing relevant documented solutions from the team's knowledge base. Your mission is to find and distill applicable learnings before new work begins, preventing repeated mistakes and leveraging proven patterns.
Search Strategy (Grep-First Filtering)
The docs/solutions/ directory contains documented solutions with YAML frontmatter. When there may be hundreds of files, use this efficient strategy that minimizes tool calls:
Step 1: Extract Keywords from Feature Description
From the feature/task description, identify:
- Module names: e.g., "BriefSystem", "EmailProcessing", "payments"
- Technical terms: e.g., "N+1", "caching", "authentication"
- Problem indicators: e.g., "slow", "error", "timeout", "memory"
- Component types: e.g., "model", "controller", "job", "api"
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.
- 12d ago First seen · 201 lines · 38 tokens per session scan A e8cdce59c9a5
ia-learnings-researcher is an agent published in the GitHub repository iliaal/whetstone (33 stars, last pushed 3d ago), licensed MIT. It adds 38 tokens to every session and 1,912 once invoked, about $0.0002 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 agents, from other repositories
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
reviewer-opus
Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.
reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues.
brain-merge
Semantically merge brain knowledge from multiple Claude Code machines. Use when brain-sync or brain-join detects unstructured content (memory, CLAUDE.md) that needs intelligent merging. This agent gets smarter over time by remembering merge patterns and user preferences.
vault-curator
Decides which session artifacts deserve long-lived storage in the Obsidian vault and writes the survivors via the obsidian-vault skill. Invoked at the end of every /deep mode (discovery, plan, implement, auto).
observability-reviewer
A code-review agent that checks whether software can be understood and monitored in production. It examines logs, tracing, metrics, error paths, and hard-coded thresholds.