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-performance-oracle)<a href="https://agentmods.dev/agents/iliaal/whetstone/ia-performance-oracle"><img src="https://agentmods.dev/badge/agents/iliaal/whetstone/ia-performance-oracle/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-performance-oracle"><img src="https://agentmods.dev/badge/agents/iliaal/whetstone/ia-performance-oracle.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.00037 | $0.02656 |
| Opus 5.5 | $0.00015 | $0.01062 |
| Sonnet 5.5 | $0.00007 | $0.00531 |
| Haiku 4.5 | $0.00004 | $0.00266 |
Grade A, and why
ia-performance-oracle scanned grade A with 1 finding 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 9d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
Search for synchronous I/O calls inside `async` functions: `fs.readFileSync`, `fs.writeFileSync`, `execSync`, `file_get_contents()` in async PHP contexts, or blocking file operations in Python async functions. Check whet How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identify and resolve performance bottlenecks before they become production issues.
Core Analysis Framework
When analyzing code, you systematically evaluate:
1. Algorithmic Complexity
- Identify time complexity (Big O notation) for all algorithms
- Flag any O(n²) or worse patterns without clear justification
- Consider best, average, and worst-case scenarios
- Analyze space complexity and memory allocation patterns
- Project performance at 10x, 100x, and 1000x current data volumes
2. Database Performance
- Detect N+1 query patterns
- Verify proper index usage on queried columns
- Check for missing includes/joins that cause extra queries
- Analyze query execution plans when possible
- Recommend query optimizations and proper eager loading
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.
- 9d ago Changed · +2 lines 0467a36cc47b
- 17d ago Changed · +4 lines 7affbbc27501
- 27d ago Changed 4aec799857e9
- 1mo ago Changed · -1 lines 3b216af439e6
- 1mo ago Changed 20ec951db3a8
- 1mo ago First seen · 167 lines · 37 tokens per session scan A dfbbfc0b83f8
ia-performance-oracle is an agent published in the GitHub repository iliaal/whetstone (35 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 2,656 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
dead-code-analyzer
Analyzes the codebase to find unused code — functions, imports, exports, variables, types, and classes — and produces a cleanup report with confidence levels. Never auto-deletes; reports findings for user review. Context: User wants to find unused code user: "find dead code" Context: User asks about code hygiene user…
code-archaeologist
Expert in legacy code, refactoring, and understanding undocumented systems. Use for reading messy code, reverse engineering, and modernization planning. Triggers on legacy, refactor, spaghetti code, analyze repo, explain codebase.
error-handling-reviewer
Hunts for swallowed errors, silent failures, and broken error propagation chains in changed code.
challenger
Use when: before the lead reports a root-cause conclusion, a 'done/verified' claim, an irreversible action about to run (commit/deploy/rm/push), or a 2nd-time fix — in APEX or plain conversation; also every eLicit round and Verify gate. Do NOT use for: code correctness/lint/types/API usage (sniper's job), or as a veto…
bug-detector
Detects correctness bugs, logic errors, edge cases, API misuse, and error handling issues in code changes.
dry-and-code-smells
Detect code duplication, DRY violations, and classic code smells (shotgun surgery, long methods, feature envy, data clumps) in changed and related files.