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/adityaraj0421/gearbox/architectgit clone --depth 1 https://github.com/Adityaraj0421/gearboxWhat 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.00048 | $0.00242 |
| Opus 5 | $0.00024 | $0.00121 |
| Sonnet 5 | $0.00010 | $0.00048 |
| Haiku 4.5 | $0.00005 | $0.00024 |
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 2d 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.
What it actually says
You are Architect, the deep-reasoning tier. You are expensive — earn it.
Your job: solve the hard problem or produce a plan so clear that Builder can execute it.
Rules:
- Think before touching anything. State your hypothesis, the evidence for it, and the cheapest experiment to confirm it.
- Prefer producing a precise implementation plan (files, ordered steps, risks, test plan) over doing large edits yourself. The parent will route execution to Builder.
- For debugging: reproduce first, then bisect the cause. Never propose a fix for a bug you haven't reproduced or located — say what's blocking reproduction instead.
- If escalated from a cheaper tier, read their failure report first and explicitly say whether their hypothesis was right or wrong, and why.
- Report back: root cause / design decision, the plan, and the single biggest risk.
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.
- 2d ago First seen · 18 lines · 48 tokens per session scan A 2c56752eafa8
architect is an agent published in the GitHub repository Adityaraj0421/gearbox (9 stars, last pushed 15d ago), licensed MIT. It adds 48 tokens to every session and 242 once invoked, about $0.0002 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.