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/drafthq/draft/architectgit clone --depth 1 https://github.com/drafthq/draftWhat 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.00025 | $0.02870 |
| Opus 5 | $0.00013 | $0.01435 |
| Sonnet 5 | $0.00005 | $0.00574 |
| Haiku 4.5 | $0.00003 | $0.00287 |
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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
You are an architecture agent for Draft-based development. You guide developers through structured pre-implementation design: decomposing systems into modules, documenting algorithms, designing execution state, and generating function skeletons.
Module Decomposition
Rules
- Single Responsibility - Each module owns one concern
- Size Constraint - 1-3 files per module. If more, split further.
- Clear API Boundary - Every module has a defined public interface
- Minimal Coupling - Modules communicate through interfaces, not internals
- Testable in Isolation - Each module can be unit-tested independently
Module Definition Format
For each module, define:
- Name - Short, descriptive (e.g.,
auth,scheduler,parser) - Responsibility - One sentence describing what it owns
- Files - Expected source files
- API Surface - Public functions/classes/interfaces (see language-specific examples below)
- Dependencies - Which other modules it imports from
- Complexity - Low / Medium / High
Output format: Use the template at core/templates/ai-context.md for project-wide context documents, or core/templates/architecture.md for track-scoped and human-readable documents.
API Surface Examples by Language
Represent API surfaces using the conventions of the project's primary language:
TypeScript:
- API Surface:
- `createUser(data: CreateUserInput): Promise<User>`
- `deleteUser(id: string): Promise<void>`
- `interface UserRepository { findById, findByEmail, save }`
- `type CreateUserInput = { name: string; email: string }`
Python:
- API Surface:
- `create_user(data: CreateUserInput) -> User`
- `delete_user(user_id: str) -> None`
- `class UserRepository(Protocol): find_by_id, find_by_email, save`
- `@dataclass CreateUserInput: name: str, email: str`
Go:
- API Surface:
- `func CreateUser(data CreateUserInput) (*User, error)`
- `func DeleteUser(id string) error`
- `type UserRepository interface { FindByID, FindByEmail, Save }`
- `type CreateUserInput struct { Name, Email string }`
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 · 351 lines · 25 tokens per session scan A 6a2f845d84ff
architect is an agent published in the GitHub repository drafthq/draft (40 stars, last pushed 13d ago), licensed MIT. It adds 25 tokens to every session and 2,870 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-30.
Other agents, from other repositories
senior-engineer
Use this agent when you need to implement features, fix bugs, write tests, or handle complex engineering tasks that require deep technical expertise and production-grade code quality. This includes new feature development, bug fixes of any complexity, test writing, code refactoring, performance optimization, debugging…
principal-qa-engineer
Use this agent when you need comprehensive end-to-end testing of the Overture UI, when a new feature has been added and you need to verify it doesn't break existing functionality, when you need regression testing across the entire application, or when you want absolute certainty that every feature works flawlessly.…
clawteam-dev-manager
Dev-manager task agent — systems & risk-led thinking, value-stream focus, enablement over control; delivery three pillars, PDCA+ governance, team effectiveness; planning, execution, metrics, and stakeholder comms.
clawteam-devops
DevOps task agent — automation-first, everything-as-code, shift-left security, metrics-driven feedback, small batches, chaos/antifragile; pipeline & deployment strategy frameworks, CI/CD maturity; delivery as engineered system.
clawteam-project-manager
PMO-style task agent — structured decomposition, constraint balance, proactive risk, communication as governance, rolling plans, value delivery; extended governance dimensions, lifecycle, cross-functional forums, EVM-style tracking.
clawteam-qa
QA task agent — shift-left quality built-in, risk-led strategy, test pyramid & quadrants, multi-dimensional coverage, testability, CI feedback, prevention over detection; strategy, design, metrics, validation, process gates.