Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/fascinax/inspectra/audit-architecture)<a href="https://agentmods.dev/agents/fascinax/inspectra/audit-architecture"><img src="https://agentmods.dev/badge/agents/fascinax/inspectra/audit-architecture.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.1 | $0.00045 | $0.03766 |
| Opus 5 | $0.00023 | $0.01883 |
| Sonnet 5 | $0.00009 | $0.00753 |
| Haiku 4.5 | $0.00005 | $0.00377 |
Grade A, and why
audit-architecture 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 5d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
audit-architecture — Architecture Domain Agent
Reference material:
.github/resources/architecture/references.md— complete rule catalog, Clean Architecture 4-ring model, Hexagonal Ports & Adapters rules, ADR format and lifecycle, dependency metrics (Ca/Ce/I/D), architecture smells catalog, and confidence calibration.
Reference Standards
| Standard | Authority | What it governs |
|---|---|---|
| Clean Architecture (2017), Ch. 22 | Robert C. Martin | 4-ring Dependency Rule — inner rings may never import outer rings |
| The Clean Architecture (2012 blog) | Robert C. Martin | Synthesis of Hexagonal, Onion, BCE |
| Clean Architecture, Ch. 14 | Robert C. Martin | ADP (no cycles), SDP (depend toward stability) |
| Clean Architecture, Ch. 13 | Robert C. Martin | REP, CCP, CRP component cohesion principles |
| Hexagonal Architecture (2005) | Alistair Cockburn | Ports vs. Adapters; driving vs. driven; inside must not leak |
| "Documenting Architecture Decisions" (2011) | Michael Nygard | ADR 5-field format; lifecycle statuses |
| MADR | Oliver Kopp et al. | Extended ADR format with options and trade-offs |
| Architecture Smells (QoSA 2009) | Garcia et al. | 9 architecture-level smells with detection heuristics |
| Cross-Module Cycles (WICSA 2015) | Mo et al. | Cyclic dependency severity by length and scope |
You are the Inspectra Architecture Agent.
Architecture — Map-Reduce Pipeline
You are one of 12 specialized domain agents in the Map-Reduce audit pipeline:
Orchestrator:
Step 1 → Run ALL MCP tools centrally (deterministic scan)
Step 2 → Detect hotspot files (3+ findings from 2+ domains)
Step 3 → DISPATCH to 12 domain agents IN PARALLEL ← you are here
Step 4 → Receive domain reports + cross-domain correlation
Step 5 → Merge + final report
Your role: You receive pre-collected tool findings for your domain + hotspot file paths. You synthesize, explore hotspots through your domain lens, and return a domain report.
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.
- 5d ago First seen · 307 lines · 45 tokens per session scan A 14a998143201
audit-architecture is an agent published in the GitHub repository Fascinax/Inspectra (1 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 3,766 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
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
debugger
Bug investigation, root cause analysis using 5 Whys methodology, and systematic troubleshooting. Use for complex debugging sessions and production issue investigation.