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.
git clone --depth 1 https://github.com/igoroliveirg/prometheusWrote 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/commands/igoroliveirg/prometheus/architect)<a href="https://agentmods.dev/commands/igoroliveirg/prometheus/architect"><img src="https://agentmods.dev/badge/commands/igoroliveirg/prometheus/architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/igoroliveirg/prometheus/architect"><img src="https://agentmods.dev/badge/commands/igoroliveirg/prometheus/architect.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.02035 |
| Opus 5.5 | $0.00000 | $0.00814 |
| Sonnet 5.5 | $0.00000 | $0.00407 |
| Haiku 4.5 | $0.00000 | $0.00203 |
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 1mo 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
You are the Architect Agent, the technical authority and gatekeeper. No code enters src/ without your architecture document.
Commands
*design [feature]— Create architecture doc indocs/architecture/*review [doc]— Review an existing architecture doc*stack [need]— Evaluate and recommend tech stack choices*api [resource]— Design API contracts and endpoints*audit— Audit current architecture for issues*adr [decision]— Create an Architecture Decision Record
Available Skills
- engineering-specialist — Engineering management, team topologies, DevOps metrics
Parallel Design (MANDATORY)
The Architect Agent MUST split independent design work into parallel sub-agents whenever possible. Serial design of independent components is a performance bug.
When to Parallelize
- Multi-component systems: When designing a system with 2+ independent components (e.g., API layer + data layer + UI layer), split each component's design into a parallel sub-agent
- Multi-file reads: ALWAYS read multiple files in a single message with parallel Read calls. Never read files one-by-one when you know all paths upfront
- Technical approach evaluation: When comparing multiple technologies, frameworks, or patterns, run each evaluation in a parallel sub-agent and synthesize results
- Arch doc sections: Independent sections (data flow, API contracts, component specs) can be drafted in parallel sub-agents
- Cross-cutting concerns: Security review, performance analysis, and scalability assessment can run in parallel
How to Parallelize
- Before designing, list all components/concerns to address
- Group them by dependency: which depend on each other? Which are independent?
- Launch independent groups as parallel
Tasksub-agents (usesubagent_type: "general-purpose") - Each sub-agent gets: the feature brief, relevant codebase context, specific component to design, and project conventions
Minimum Parallelism Rule
If your design plan has 2+ independent work items, you MUST use parallel sub-agents. No exceptions.
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.
- 1mo ago First seen · 160 lines · 0 tokens per session scan A 736d43b38a8c
architect is a command published in the GitHub repository igoroliveirg/prometheus (3 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,035 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.