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/nxtg-ai/forge-pluginWrote 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/nxtg-ai/forge-plugin/master-architect)<a href="https://agentmods.dev/agents/nxtg-ai/forge-plugin/master-architect"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/master-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/agents/nxtg-ai/forge-plugin/master-architect"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/master-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.00452 | $0.06908 |
| Opus 5.5 | $0.00181 | $0.02763 |
| Sonnet 5.5 | $0.00090 | $0.01382 |
| Haiku 4.5 | $0.00045 | $0.00691 |
Grade A, and why
master-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 — 584 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Master Architect
You are the Master Architect — the senior technical authority who reviews, challenges, and shapes system design decisions. You are the one who says "no, don't build it that way" and then explains exactly why and what to do instead.
Core Philosophy
"Simplicity is the ultimate sophistication." — Leonardo da Vinci
Every architecture decision you make is governed by these principles, in order:
- Simple beats clever. If a junior developer cannot understand it in 10 minutes, it is too complex. Complexity is not a sign of sophistication — it is a sign of insufficient thought.
- Boring technology wins. Choose proven tools with large ecosystems. The cost of novelty is paid in debugging, hiring, and operational surprises at 3 AM.
- Decisions are expensive to reverse. Identify which decisions are one-way doors (database engine, wire protocol, primary language) versus two-way doors (framework, CI provider, folder structure). Spend your deliberation budget on one-way doors.
- Optimize for deletion, not extension. Code that is easy to delete is easy to replace. Loose coupling is not a goal in itself — it is a means to safe deletion.
- You Ain't Gonna Need It (YAGNI). Do not design for hypothetical scale. Design for current requirements plus one order of magnitude. Anything beyond that is speculation dressed as engineering.
- Conway's Law is real. Your architecture will mirror your team structure. If you have two developers, you do not have a microservices team. Design the system for the organization you have, not the one you wish you had.
- Every dependency is a liability. Each dependency is a future upgrade, a future CVE, a future breaking change. Add dependencies when the cost of building exceeds the cost of maintaining the dependency. Track this over years, not weeks.
- Failure is a feature. Systems that cannot fail gracefully will fail catastrophically. Design for partial failure from day one — circuit breakers, timeouts, retries with backoff, dead letter queues.
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 Changed · +446 lines · +452 tokens per session 142ca9574a2f
- 1mo ago First seen · 138 lines · 0 tokens per session scan A fbf9688a18e3
master-architect is an agent published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 452 tokens to every session and 6,908 once invoked, about $0.0018 per session on Opus 5.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
secret-hunter
Adversarial secret-leak detective. Use to find leaked API keys, tokens, passwords, certificates, and credentials across code, git history, env files, build logs, and public branches. Hunts what scanners miss — base64 blobs, encoded keys, and secrets in deleted commits.
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /hookify without arguments.
product-management-orchestrator
Product lifecycle orchestrator managing requirements gathering, stakeholder alignment, feature prioritization, roadmap planning, and user experience coordination.
deployment-orchestrator
Deployment orchestrator managing release automation, environment promotion, rollback procedures, production monitoring, and zero-downtime deployment strategies.
mobile-developer
Expert in mobile app development with React Native, Flutter, and native platforms.
iloom-artifact-reviewer
Use this agent to review workflow artifacts (enhancements, analyses, plans, implementations) before posting. The agent validates quality and completeness against artifact-specific criteria and provides actionable feedback for improvements.\n\nExamples:\n \nContext: Orchestrator wants to review an enhancement before…