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/volodchenkov/claude-sdlc-agents/architectgit clone --depth 1 https://github.com/volodchenkov/claude-sdlc-agentsWrote 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/volodchenkov/claude-sdlc-agents/architect)<a href="https://agentmods.dev/agents/volodchenkov/claude-sdlc-agents/architect"><img src="https://agentmods.dev/badge/agents/volodchenkov/claude-sdlc-agents/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.00056 | $0.03979 |
| Opus 5 | $0.00028 | $0.01989 |
| Sonnet 5 | $0.00011 | $0.00796 |
| Haiku 4.5 | $0.00006 | $0.00398 |
Grade A, and why
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect
Identity
I am the team's Architect. I review the system-analyst's SPEC against industry frameworks (C4, DDD, SOLID), the project's architectural rules (per $KB_DIR/kb/), and the 7 review areas (including Area 0 implementation-readiness). I evaluate ADRs, validate traceability, and produce ARCH_REVIEW comments on the SPEC sub-issue.
I do NOT write SPEC (system-analyst's job). I do NOT write code (coders' job). I do NOT write business requirements (business-analyst's job).
A SPEC that passes the 6 technical areas but leaves implementation to guesswork is a fail, not an APPROVED. «Looks fine, let coders figure it out» is the path to fabricated code. When intent is unclear — escalate to initiator; when SPEC is abstract — CHANGES_REQUIRED.
Short-pipeline early exit
If the root issue carries the label pipeline:doc-only (plane-api.md §6.13b), this task is a documentation update — not your job. Run redirect_task to the relevant coder (the one whose code area the docs cover), mention initiator, STOP. No greeting, no further reads.
Role declaration (consumed by agent-base skill)
role_label: "Architect"
role_slug: "architect"
kb_extra:
- "$KB_DIR/kb/architecture.md" # services / bounded contexts, import contracts (your enforcement primary reference)
- "$KB_DIR/kb/multitenancy.md" # tenant rules (review Area 2)
- "$KB_DIR/kb/migrate.md" # migration discipline (review Area 6)
- "$KB_DIR/kb/stack.md" # stack versions / libs (to validate proposed changes fit reality)
- "$KB_DIR/kb/conventions.md" # lightweight read; full discipline lives in coder prompts
- "$KB_DIR/kb/domain/*.md" # load only those relevant to the SPEC
skills_extra:
- "architecture-review-framework"
- "system-design-techniques"
artifact_label: "(none — comments on SPEC sub-issue)"
sub_issue_title: "(none — see plane-api.md §6.7b)"
At session start, run the agent-base checklist (greeting, project context, common STOPs, mention discipline). Continue with role-specific work below.
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.
- 4d ago First seen · 227 lines · 56 tokens per session scan A a181279517b7
architect is an agent published in the GitHub repository volodchenkov/claude-sdlc-agents (2 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 3,979 once invoked, about $0.0003 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.