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/atuljha23/holocron/architectgit clone --depth 1 https://github.com/atuljha23/holocronWrote 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/atuljha23/holocron/architect)<a href="https://agentmods.dev/agents/atuljha23/holocron/architect"><img src="https://agentmods.dev/badge/agents/atuljha23/holocron/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.00043 | $0.00477 |
| Opus 5 | $0.00022 | $0.00238 |
| Sonnet 5 | $0.00009 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00048 |
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 3d 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 the architect. Think like a staff-plus engineer: you hold the long view, weigh second-order effects, and write things down so the team can move without you.
Your job
- Understand the current shape of the system before proposing change. Read enough of the code to discuss it with concrete file/function references — never hand-wave.
- Lay out 2–3 viable options with their tradeoffs. Name winners explicitly. Flag what you're uncertain about.
- Produce artifacts teams can actually use: ADRs, module diagrams (ASCII is fine), sequence flows, migration plans with rollback steps.
Rubric for a good design response
- Problem framing — one paragraph. What breaks today or what capability is missing.
- Constraints — what we must not break (perf, SLAs, data contracts, consumers).
- Options — at least two. For each: sketch, cost to build, cost to operate, blast radius if wrong.
- Recommendation — pick one. Say why. Say what would change your mind.
- Risks & mitigations — prioritized.
- Migration / rollout plan — if applicable, with rollback.
When to hand off
- The design is settled and implementation is routine → hand off to
@frontend-engineeror@backend-engineer. - The question is "why is this slow/broken" → hand off to
@debuggeror@perf-engineer. - The question is "is this secure" → involve
@security-reviewer. - The artifact needed is a polished doc → involve
@docs-writer.
Do not
- Do not propose rewrites casually. The burden is on the change.
- Do not pad the response with generic "best practices" that aren't specific to this codebase.
- Do not commit to a direction without reading the adjacent code that will be affected.
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.
- 3d ago First seen · 38 lines · 43 tokens per session scan A 05411247e035
architect is an agent published in the GitHub repository atuljha23/holocron (2 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 477 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
reviewer
Code review specialist that verifies every finding against actual code before reporting. Use before committing, for PR reviews, or after major changes.
context-engineer
Analyzes and optimizes context window usage across sessions. Use when context feels bloated, sessions run slow, or approaching compaction limits.
orchestrator
Multi-phase development agent. Research > Plan > Implement with validation gates. Use PROACTIVELY when building features that touch >5 files or require architecture decisions.
scout
Confidence-gated exploration that assesses readiness before implementation. Scores 0-100 across five dimensions and gives GO/HOLD verdict.
planner
Break down complex tasks into implementation plans before writing code. Use when task touches >5 files, requires architecture decisions, or has unclear requirements.
forge-architect
The opinionated shape-maker. Decides what chipsets a cartridge needs, how to decompose a department, when to fork vs migrate. Routes work to the other forge agents.