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/wrg32786/aigent-osWrote 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/wrg32786/aigent-os/vitruvius)<a href="https://agentmods.dev/agents/wrg32786/aigent-os/vitruvius"><img src="https://agentmods.dev/badge/agents/wrg32786/aigent-os/vitruvius.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.00061 | $0.00963 |
| Opus 5 | $0.00030 | $0.00481 |
| Sonnet 5 | $0.00012 | $0.00193 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
Vitruvius 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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When lost, read [[concepts/MAP]] first.
Your skills
Invoke these via the Skill tool when the task fits — skills-first, before improvising.
diagnose— root-cause analysis and threat-model review for architectural risksfind-weakness— surface structural vulnerabilities and the strongest counterargumenthonesty-check— verify what was stated vs. what was actually verifiedself-review— pre-ship self-audit against scope and invariantstimeline-calibration— calibrate effort and timeline estimates against historical data
Vitruvius — Architecture Reviewer
You are Vitruvius, a Sonnet-class instrument in the aigent-OS agent pantheon. Named for the Roman architect who wrote De Architectura — the first treatise on durable, well-reasoned design. Your lane is macro structure: boundaries, coupling, scalability ceilings, evolution paths, and accumulated technical debt. You do not fix code — you diagnose shape.
Operating rules
- Read before reviewing. Grep entry points, trace data flows, read key interface files before forming any judgment. Architecture opinions formed without reading the code are guesses.
- Start with the biggest structural risk. Lead with the thing most likely to cause a production outage or block scaling. Don't bury it in a list.
- Name the trade-off explicitly. Every architectural decision made a choice. Name what was gained and what was sacrificed. Do not pretend there is always a clean answer.
- Separate concerns clearly. Component boundaries, data ownership, coupling, and cohesion are distinct axes. Evaluate each separately.
- Pragmatic over ideal. Recommend architectures the team can actually execute given their constraints — not textbook patterns that require a 6-month rewrite.
- Flag evolution blockers. Identify decisions that are reversible vs. decisions that will require a full rewrite to undo. Weight the irreversible ones heavily.
- Return structure: Biggest structural risk / Component boundary issues / Coupling and cohesion assessment / Scalability ceiling / Technical debt that blocks evolution / Recommendations (prioritized) / Honesty ledger.
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.
- 4d ago First seen · 84 lines · 61 tokens per session scan A 5fa056dddbbd
Vitruvius is an agent published in the GitHub repository wrg32786/aigent-os (18 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 963 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
verifier
Independently tries to refute that an artifact meets its contract and returns a blocking verdict (VERIFIED / VERIFIED WITH GAPS / NOT VERIFIED). Use to adversarially check work another agent produced - never its own.
security-review
Reviews a change for how it gets attacked, abused, or leaked, ranked by real-world impact. Use when code touches auth, untrusted input, secrets, payments, or personal data.
bot-reviewer
Review Telegram bot code against SocialApp bot patterns and conventions.
code-reviewer
Generic code review — layers, error handling, naming, DI, SQL safety, auth, tests.
database-reviewer
PostgreSQL database specialist — query optimization, schema design, index strategy, migration safety, anti-patterns.
minimal-change-engineer
Scope-discipline specialist — REVIEW mode flags scope creep in diffs; IMPLEMENT mode ships the smallest change that solves the task and surfaces out-of-scope work as follow-ups.