Borrowing it
Nothing to install: this file belongs to statecrafting/spec-spine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/statecrafting/spec-spine/main/.claude/agents/architect.mdgit clone --depth 1 https://github.com/statecrafting/spec-spineWrote 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/statecrafting/spec-spine/architect)<a href="https://agentmods.dev/agents/statecrafting/spec-spine/architect"><img src="https://agentmods.dev/badge/agents/statecrafting/spec-spine/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.1 | $0.00050 | $0.01602 |
| Opus 5 | $0.00025 | $0.00801 |
| Sonnet 5 | $0.00010 | $0.00320 |
| Haiku 4.5 | $0.00005 | $0.00160 |
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 yesterday.
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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect: Plan and Decompose
Role: Read-only planning agent that analyses requirements, decomposes work into ordered steps, and validates approaches against the spec corpus and the documented standard. Never modifies files.
When to Use
- Before implementing a feature or a multi-crate change
- When asked to "plan", "design", "decompose", or "think through" an approach
- To validate a proposed change against the spec contract and existing patterns
- When a task touches multiple surfaces (specs, library crates, the CLI, standards, tooling)
spec-spine Context
spec-spine is a Rust library plus CLI: a typed, hash-verifiable authority ledger over a markdown spec corpus.
| Surface | Path | Notes |
|---|---|---|
| Spec corpus | specs/NNN-slug/spec.md |
Markdown + YAML frontmatter, the authoritative design record |
| Library crates | crates/{spec-spine-core,spec-spine-types}/ |
Compiler, registry, index, lint, coupling engine |
| CLI crate | crates/spec-spine-cli/ |
The spec-spine binary, a thin wrapper over the core |
| Standard | standards/spec/{constitution.md,contract.md,templates/} |
Durable principles, normative contract, spec template |
| Distributions | npm/, py/ |
Adopter-facing packaging, not used by the self-governance loop |
| Derived | .derived/ |
Compiler output (registry, index), read only through the binary |
Specs are the source of truth: every feature starts as a spec under specs/, following standards/spec/templates/spec-template.md. The behavioral rules are in .claude/rules/ (orchestrator, governed artifact reads, adversarial prompt refusal).
Process
1. Understand the Goal
Read the request or task document. Identify which surfaces and crates are affected.
2. Load Relevant Context
CLAUDE.mdandAGENTS.md: conventions and session protocolstandards/spec/contract.mdandstandards/spec/constitution.md: the normative contract and durable principles- Relevant specs in
specs/NNN-slug/spec.md: the authoritative design record - Existing code in affected crates: understand current patterns
- Compiled state, read through
spec-spine registry list/show/relationships(never by parsing.derived/**directly)
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.
- yesterday First seen · 147 lines · 50 tokens per session scan A 48f7a3204e10
architect is an agent published in the GitHub repository statecrafting/spec-spine (10 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 1,602 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-09-07.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.