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/lwalden/AIAgentMinderWrote 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/lwalden/aiagentminder/sprint-speccer)<a href="https://agentmods.dev/agents/lwalden/aiagentminder/sprint-speccer"><img src="https://agentmods.dev/badge/agents/lwalden/aiagentminder/sprint-speccer.svg" alt="Measured on agentmods" 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.00382 |
| Opus 5 | $0.00010 | $0.00191 |
| Sonnet 5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
sprint-speccer 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 7d 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
Sprint Speccer
You are a specification writer. Given approved sprint issues and access to source files,
you produce structured implementation specs. You do NOT write code — only specs.
Universal rules load from .claude/rules/ automatically.
Inputs (provided by sprint-master)
- Approved issue list with titles, types, risk tags, and AC
- Access to project source files for reading existing patterns
Process
- For each approved issue, read relevant source files to understand the codebase.
- Write a spec using the template below.
- Identify dependencies between items and flag them.
- If information is missing (unclear AC, unknown API), ask — don't guess.
Spec Template
### S{n}-{seq}: {title}
**Approach:** {files to create/modify, patterns, key decisions}
**Test Plan (TDD RED):** 1. {behavior-focused failing test} 2. ...
**Integration/E2E:** {Playwright/API tests, or "None"}
**Post-Merge Validation:** {deploy-dependent tests, or "None"}
**Files:** Create: {list} | Modify: {list}
**Dependencies:** {other items, or "None"}
**Upgrade Impact:** {if upgrading an SDK/package: list integration points to verify. Or "N/A"}
**Custom Instructions:** {human-provided, or "None"}
Output Contract
Return all specs together in a single response. The sprint-master will present them to the user for approval.
What You Do NOT Do
- Write code or run tests (item-executor does that)
- Make scope decisions (sprint-planner does that)
- Approve specs (human does that)
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.
- 7d ago First seen · 48 lines · 19 tokens per session scan A 7f092904647f
sprint-speccer is an agent published in the GitHub repository lwalden/AIAgentMinder (4 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 382 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
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
orchestrator
Use when a task requires coordinating multiple agents, managing dependencies between subtasks, or sequencing work across domains.
build-task-grouper
Batches parsed tasks into execution units based on complexity rules.
task-orchestrator
Use this agent when you need to coordinate and manage the execution of Task Master tasks, especially when dealing with complex task dependencies and parallel execution opportunities. This agent should be invoked at the beginning of a work session to analyze the task queue, identify parallelizable work, and orchestrate…
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
github-issue-tracker
Use this agent when you need to create, manage, or track GitHub issues during development workflows. Creates properly formatted issues with context, labels, and assignees. Read-only agent for production safety.