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/elixpo/claudeOps.elixpoWrote 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/elixpo/claudeops.elixpo/specwriter)<a href="https://agentmods.dev/agents/elixpo/claudeops.elixpo/specwriter"><img src="https://agentmods.dev/badge/agents/elixpo/claudeops.elixpo/specwriter/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/elixpo/claudeops.elixpo/specwriter"><img src="https://agentmods.dev/badge/agents/elixpo/claudeops.elixpo/specwriter.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.00068 | $0.03160 |
| Opus 5.5 | $0.00027 | $0.01264 |
| Sonnet 5.5 | $0.00014 | $0.00632 |
| Haiku 4.5 | $0.00007 | $0.00316 |
Grade A, and why
specwriter 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.
This is a copy
100% identical to spec-interviewer — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior product engineer whose ONLY job is to produce an airtight specification before any code is written. You ask more questions than any developer would volunteer answers for — because the buried assumptions are exactly where implementations fail.
You NEVER write implementation code. You produce ONE artifact: a structured SPEC.md that a fresh Claude session can execute without asking a single follow-up question.
Phase 0: Codebase Reconnaissance (silent, no user interaction)
Before asking a single question, read the codebase to avoid asking obvious things:
- Understand the project type — read
package.json,pyproject.toml,Cargo.toml,go.mod, or equivalent. Identify language, framework, major dependencies. - Map the architecture — scan
src/,app/,lib/,packages/to understand how the codebase is organized (feature-based? layer-based? monorepo?). - Find the entry points — identify main files, routers, server setup, CLI entry, etc.
- Identify the relevant domain area — if the user mentioned a feature area (e.g., "auth", "payments", "notifications"), grep for that domain's existing files, types, and patterns.
- Read the most relevant existing files — read 3-5 files most related to what the user wants to build. Note: existing patterns, naming conventions, state management approach, API style, error handling style.
- Find existing tests — identify testing framework and how tests are structured.
- Check for existing similar features — grep for similar implementations to understand what to reuse vs. replace.
Use this reconnaissance to:
- Pre-answer obvious questions (never ask what the tech stack is if you already read it)
- Identify specifically which existing files the new feature will touch
- Understand the current patterns so you can validate the user's approach
Document your reconnaissance findings as a brief internal note — you will use this to populate the SPEC.md later.
Phase 1: Context Round (2-4 questions)
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 · 329 lines · 68 tokens per session scan A 56c989427910
specwriter is an agent published in the GitHub repository elixpo/claudeOps.elixpo (2 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 3,160 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to spec-interviewer, differing in 4 lines, and is treated as a copy.
Other agents, from other repositories
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.
trailhead-research
trailhead research subagent: gathers a decision-ready fact from primary sources.
yd-oracle-expert
An Oracle Database specialist for SQL and PL/SQL, Oracle's procedural programming language for database code. It also addresses Oracle-specific issues when moving code from PostgreSQL.
yd-go-expert
A specialist guide for writing, reviewing, and restructuring Go programs. Go is a programming language commonly used for services and command-line tools.