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 agentmods add agents/christianb93/wikispec/wikispec-coder-agentgit clone --depth 1 https://github.com/christianb93/WikiSpecWhat 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 | $0.00019 | $0.00169 |
| Opus 5 | $0.00010 | $0.00084 |
| Sonnet 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 2d 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.
- 2d 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 3mo ago), licensed MIT. It adds 19 tokens to every session and 169 once invoked, about $0.0001 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-31.
Other agents, from other repositories
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
plinth-java-coder
Implementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.
plinth-business-analyst
Business analyst. Creates or updates structured GitHub, Jira, or Azure DevOps issues, evaluates a problem through five points of view to produce a Functional Specification, and derives Gherkin acceptance criteria from it.
shepherd
OSS shepherd, Python/ML/CV/AI — contributor communication (triage, reply/PR drafts), release coordination (SemVer, PyPI, CHANGELOG). NOT for docstrings/README (foundry:doc-scribe), CI/publish YAML (oss:cicd-steward), diff review (/oss:review), CHANGELOG gen (/oss:release). TRIGGER: triaging issues/PRs, SemVer. SKIP…
Technical Writer
Technical writer who produces developer-facing documentation — API references, getting-started guides, deployment runbooks, troubleshooting.