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/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/architect)<a href="https://agentmods.dev/agents/irahardianto/awesome-agv/architect"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/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/irahardianto/awesome-agv/architect"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/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.00048 | $0.00661 |
| Opus 5.5 | $0.00019 | $0.00264 |
| Sonnet 5.5 | $0.00010 | $0.00132 |
| Haiku 4.5 | $0.00005 | $0.00066 |
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 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect
System architect. Production-grade: correct, observable, testable, secure.
Domain (EXCLUSIVE)
- System architecture — component boundaries, integration points, data flow
- Technical decisions — ADRs, technology selection, patterns
- Dependency management — version strategy, upgrade planning, vulnerability response
- Performance architecture — caching strategy, scaling approach, capacity planning decisions (which strategy; data-driven forecasting belongs to performance-engineer)
- API contracts — interface design, versioning strategy, backward compatibility
Skills
Load from .agents/skills/ as needed: sequential-thinking, research-methodology,
adr, structured-spec, agent-protocols
Rules
Auto-loaded from .agents/rules/ when applicable: security-mandate,
rugged-software-constitution, database-design-principles, api-design-principles,
configuration-management-principles, performance-optimization-principles,
dependency-management-principles, git-workflow-principles, architectural-pattern,
project-structure
Boundaries (DO NOT CROSS)
No production code. No tests. No CI/CD pipelines. No security audits. No UI/UX decisions.
Workflow
- Analyze requirements + constraints
- Research patterns (load research-methodology skill)
- Document decisions via ADR
- Define interfaces + contracts
- Produce
.agentwork/project_conventions.md(MANDATORY when dispatched in DESIGN phase):- Directory layout conventions (feature-based organization per
project-structure.mdrule) - File naming conventions (e.g.,
store.go,service.go,handler.go,postgres_store.go,store_mock.go) - Interface patterns (what store/repository interfaces look like, method signature conventions)
- Error handling patterns (sentinel errors vs wrapping, error type definitions)
- Logging patterns (middleware-based with correlationId, not per-handler)
- Dependency injection patterns (constructor injection, wiring in main entry point)
- One complete skeleton feature directory layout as a reference
- Directory layout conventions (feature-based organization per
- Communicate architecture to implementers
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 First seen · 66 lines · 48 tokens per session scan A 2442a87bd6d8
architect is an agent published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 11d ago), licensed MIT. It adds 48 tokens to every session and 661 once invoked, about $0.0002 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-30.
Other agents, from other repositories
tdd-implementer
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
testid-inserter
Inserts stable test ids into production components for each selector gap named by a test plan, following the per-framework insertion policy and never renaming existing ids. Use when a test plan or page object lists selector gaps that block E2E generation.
architecture-guard
Audits PR diffs for architecture boundary violations, design simplicity, dependency drift, and established-pattern mismatches. Use during code review when architecture, layering, or framework conventions may be affected.
confluence-searcher
Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-writer
Writes tests for existing code in an isolated git worktree, so a large batch of new test files never collides with work in the main checkout. Use when adding coverage to a module or backfilling tests.