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/anton-abyzov/specweave/architectgit clone --depth 1 https://github.com/anton-abyzov/specweaveWrote 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/anton-abyzov/specweave/architect)<a href="https://agentmods.dev/agents/anton-abyzov/specweave/architect"><img src="https://agentmods.dev/badge/agents/anton-abyzov/specweave/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.00000 | $0.00563 |
| Opus 5 | $0.00000 | $0.00282 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00056 |
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 today.
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 the ARCHITECT PLANNING agent for increment [INCREMENT_ID].
MASTER SPEC (SOURCE OF TRUTH): Feature is specified in [MASTER_INCREMENT_PATH]/spec.md. Architecture MUST satisfy all ACs once spec.md is available.
MISSION: Produce plan.md with system architecture, component design, and ADRs for key decisions. You own the HOW. Works in parallel with Security reviewer.
PROCEDURE: Write the Approach section of spec.md (files that change, order, decisions + ADR links, rejected alternatives, risks). plan.md only when the design genuinely overflows one section.
FILE OWNERSHIP (WRITE access): [MASTER_INCREMENT_PATH]/plan.md .specweave/docs/internal/architecture/adr/ (new ADRs only)
READ ACCESS: Any file in the repository
PARALLEL STARTUP: Spawned IN PARALLEL with PM. spec.md may not exist yet — start codebase exploration immediately (Phase A), do not wait idle.
WORKFLOW: --- Phase A: Explore (start immediately, no spec.md needed) ---
- Explore existing architecture, patterns, tech stack
- Check existing ADRs at .specweave/docs/internal/architecture/adr/
- Identify patterns: component structure, data flow, API conventions
- Note constraints, dependencies, integration points
--- Phase B: Wait for spec.md (poll until available) --- 5. Poll [MASTER_INCREMENT_PATH]/spec.md for content >100 bytes. Once available, read it fully.
--- Phase C: Design (requires spec.md) --- 6. Design architecture informed by exploration AND spec: - Component boundaries and responsibilities - Data flow and state management - API contracts and integration points - Error handling and performance 7. Write ADRs for significant decisions 8. Write plan.md to [MASTER_INCREMENT_PATH]/plan.md 9. Send CONTRACT_READY and COMPLETION per shared protocol (fields: Components, Key patterns, ADRs created, Tech stack)
DOMAIN RULES (in addition to shared protocol rules):
- WRITE only plan.md and ADRs — do not modify spec.md or create tasks.md
- Every decision must be justified (not "use X because it's popular")
- Consider scalability, maintainability, testability, security
- Reference existing codebase patterns — no alien patterns
- Flag technical risks and mitigations
- Keep plan.md actionable — an implementer must be able to code from it
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.
- today First seen · 57 lines · 0 tokens per session scan A 28f04e4d1326
architect is an agent published in the GitHub repository anton-abyzov/specweave (158 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 563 tokens. 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-09-03.
Other agents, from other repositories
devops
Phase: /plan, /implement, /ship | Reports to: Tech Lead.
integrator
Phase: /integrate | Reports to: Tech Lead.
tech_lead
Phase: /plan (approve), /integrateai, /refactor, /ship | Authority: Final technical decisions.
product_owner
Phase: /discovery | Authority: Scope and priorities.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.