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/viksant/vibe-coding-tools-content/architect-reviewgit clone --depth 1 https://github.com/viksant/vibe-coding-tools-contentWrote 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/viksant/vibe-coding-tools-content/architect-review)<a href="https://agentmods.dev/agents/viksant/vibe-coding-tools-content/architect-review"><img src="https://agentmods.dev/badge/agents/viksant/vibe-coding-tools-content/architect-review.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.00048 | $0.02321 |
| Opus 5 | $0.00024 | $0.01161 |
| Sonnet 5 | $0.00010 | $0.00464 |
| Haiku 4.5 | $0.00005 | $0.00232 |
Grade A, and why
architect-review 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 233 lines · 48 tokens per session scan A 1dac7f6ac6bc
architect-review is an agent published in the GitHub repository viksant/vibe-coding-tools-content (44 stars, last pushed 2mo ago), with no licence file. It adds 48 tokens to every session and 2,321 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-30.
Other agents, from other repositories
performance-tuner
Performance triage specialist — profile-driven hotspot analysis for confirmed bottlenecks. Refuses speculative optimization requests by demanding profiling evidence first. Invoke when you have a profile (flame graph, allocation report, query log, benchmark) and need a ranked hotspot read with optimization…
accessibility-auditor
Accessibility audit specialist — depth-first WCAG 2.2 AA review of frontend diffs for ARIA misuse, focus mismanagement, color contrast, and screen-reader anti-patterns. Invoke when you want a focused a11y report, not a holistic code review.
test-reviewer
Test audit specialist — depth-first review of test suites for flakiness, over-mocking at internal boundaries, behaviour-vs-implementation drift, and coverage gaps. Invoke when you want a focused test audit, not authoring new tests.
tech-writer
Documentation author — generates README sections, ADRs, ARCHITECTURE/OVERVIEW, and non-obvious inline comments from diffs and conversation context, matching the repo's existing tone and conventions. Invoke when documentation is missing, stale, or drifting from code.
bc-developer
Implements BC components using TDD workflow. Reads the canonical Phase 3 spec at {coachoutputroot}/{bc}/spec.md plus the .claude/rules/{bc}.md quick-reference card and CLAUDE.md, then follows Red-Green-Refactor per Aggregate vertical slice. Stack-agnostic skeleton — all stack-specific commands (test runner, ORM…
Demonstrate
Agent for demonstrating VS Code features.