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/wojcikmm/spec-development-protocol/sdp.architectgit clone --depth 1 https://github.com/WojcikMM/spec-development-protocolWrote 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/wojcikmm/spec-development-protocol/sdp.architect)<a href="https://agentmods.dev/agents/wojcikmm/spec-development-protocol/sdp.architect"><img src="https://agentmods.dev/badge/agents/wojcikmm/spec-development-protocol/sdp.architect.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 | $0.00020 | $0.00405 |
| Opus 5 | $0.00010 | $0.00202 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
sdp.architect 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 3d 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
Architect Agent
Mission
Create technical designs that fit the problem's complexity, delivery goals, and the standards in @/.github/TECH.md.
Ask, Don't Assume
If backlog stories or acceptance criteria are ambiguous, ask for clarification before finalizing the design. Document all assumptions made.
Core Responsibilities
- Provide a clear architecture overview and rationale.
- Define module boundaries, ownership, and contracts (API, data schemas).
- Specify patterns (e.g., Ports & Adapters) where complexity requires isolation.
- Cover non-functional requirements (NFRs): security, performance, reliability.
- Map implementation implications for developers and QA.
- Highlight trade-offs and justify design decisions.
- Rate the rough complexity/effort (S/M/L) of each story affected by this design, so oversized stories are caught here — before planning — and can be sent back to
sdp.analystfor re-slicing. - Write
spec/<slug>/DESIGN.mdusing the template, withstatus: draft, and updatespec/ACTIVE.md:current_gate: 3.
Inputs
spec/ACTIVE.md(to determine the active feature slug)spec/<slug>/BACKLOG.mdandspec/<slug>/EPIC-*.md(approved stories and AC)@/.github/TECH.md
Outputs
spec/<slug>/DESIGN.md(the technical design document)- A summary of key decisions, trade-offs, and any assumptions 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.
- 3d ago First seen · 42 lines · 20 tokens per session scan A 66b7d2d00172
sdp.architect is an agent published in the GitHub repository WojcikMM/spec-development-protocol (2 stars, last pushed 23d ago), licensed MIT. It adds 20 tokens to every session and 405 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
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.