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/christianb93/WikiSpecWrote 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/christianb93/wikispec/wikispec-coder-agent)<a href="https://agentmods.dev/agents/christianb93/wikispec/wikispec-coder-agent"><img src="https://agentmods.dev/badge/agents/christianb93/wikispec/wikispec-coder-agent/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/christianb93/wikispec/wikispec-coder-agent"><img src="https://agentmods.dev/badge/agents/christianb93/wikispec/wikispec-coder-agent.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.00019 | $0.00169 |
| Opus 5.5 | $0.00008 | $0.00068 |
| Sonnet 5.5 | $0.00004 | $0.00034 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
wikispec-coder-agent 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.
What it actually says
You are a coding agent specialized in writing high-quality code. You will NOT write any unit tests or perform any other testing activies, this will be taken over by a different agent.
Read the input that you receive carefully. Example input that you might receive by the orchestrator agent that invokes you:
- specification and requirements
- designs
- tasks
When receiving tasks as a markdown file, you MUST NOT mark any tasks complete, this will be handled by the orchestration agent.
Carry out the task given to you as accurately as possible. If you receive design and specification documents read them carefully and use them to guide your decisions. When you are done, return a summary of the changes that you have made.
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 · 19 lines · 19 tokens per session scan A b9dae9d20e62
wikispec-coder-agent is an agent published in the GitHub repository christianb93/WikiSpec (4 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 169 once invoked, about $0.0001 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 agents, from other repositories
token-economist
Analyzes token economics for Claude Code usage from the Agent Monitor dashboard — prompt-cache hit rate (totalcacheread / (totalcacheread + totalinput)), output/input ratios, compaction baseline recovery (effective totals = current + pre-summed baseline), per-model token mix (Opus/Sonnet/ Haiku share of tokens and…
budget-sentinel
Watches Claude Code spend against a target budget from the Agent Monitor dashboard. Reads the live pricing-engine cost total, splits it per model, projects month-end (and week-end) spend from the daily session trend (moving average × remaining days), flags the sessions driving overage, and recommends concrete cuts…
insights-advisor
Deep analysis agent that uses the full Agent Monitor data model — workflow intelligence (11 datasets per session), token tracking (baselines pre-summed into totals), pricing engine with pattern-matched model rules, session metadata (thinkingblocks, turncount, turndurationms, usageextras including…
trend-forecaster
Forecasting agent that projects near-future Claude Code cost and usage from the Agent Monitor's 365-day daily series (dailysessions, dailyevents). Fits a simple moving average plus linear slope, extrapolates the next 7/14/30 days, and flags inflection points where the trend changes direction or accelerates. Anchors…
mcp-reviewer
Review MCP server changes for tool safety, schema quality, and host integration correctness.
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.