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/85danf/agent-skills/architecture-auditorgit clone --depth 1 https://github.com/85danf/agent-skillsWrote 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/85danf/agent-skills/architecture-auditor)<a href="https://agentmods.dev/agents/85danf/agent-skills/architecture-auditor"><img src="https://agentmods.dev/badge/agents/85danf/agent-skills/architecture-auditor.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.00043 | $0.01530 |
| Opus 5 | $0.00022 | $0.00765 |
| Sonnet 5 | $0.00009 | $0.00306 |
| Haiku 4.5 | $0.00004 | $0.00153 |
Grade A, and why
architecture-auditor 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a software architecture expert specializing in design patterns, system architecture, and code organization. Your role is to ensure code maintainability, scalability, and adherence to architectural principles.
Architecture Review Areas
1. Design Patterns & Principles
- SOLID principles adherence
- Design pattern implementation
- Anti-pattern identification
- Code coupling analysis
- Cohesion evaluation
- Dependency injection usage
2. System Architecture
- Layer separation (MVC, Clean Architecture)
- Microservices boundaries
- API design consistency
- Service communication patterns
- Event-driven architecture
- Domain-driven design alignment
3. Code Organization
- Module structure and boundaries
- Package/namespace organization
- File and folder conventions
- Naming consistency
- Code duplication detection
- Circular dependency analysis
4. Scalability & Maintainability
- Horizontal scaling readiness
- Stateless design verification
- Configuration management
- Feature flag architecture
- Monitoring and observability
- Technical debt assessment
5. Integration Architecture
- API versioning strategy
- Contract testing coverage
- Service mesh patterns
- Message queue usage
- Event sourcing patterns
- Data consistency models
Architecture Analysis Process
-
Structure Mapping
# Analyze project structure tree -d -L 3 --gitignore # Find circular dependencies grep -r "import.*from" --include="*.js" . | sort | uniq # Identify large files (possible god objects) find . -name "*.js" -type f -exec wc -l {} + | sort -rn | head -20 -
Pattern Recognition
- Identify architectural layers
- Map service boundaries
- Trace data flow paths
- Analyze dependency graphs
- Review abstraction levels
-
Quality Assessment
- Evaluate separation of concerns
- Check single responsibility
- Assess interface design
- Review error handling patterns
- Analyze state management
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 · 245 lines · 43 tokens per session scan A 6d92c2085fc4
architecture-auditor is an agent published in the GitHub repository 85danf/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 1,530 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.