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/rosudrag/ai-praxisWrote 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/rosudrag/ai-praxis/architect)<a href="https://agentmods.dev/agents/rosudrag/ai-praxis/architect"><img src="https://agentmods.dev/badge/agents/rosudrag/ai-praxis/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/rosudrag/ai-praxis/architect"><img src="https://agentmods.dev/badge/agents/rosudrag/ai-praxis/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.00014 | $0.00772 |
| Opus 5.5 | $0.00006 | $0.00309 |
| Sonnet 5.5 | $0.00003 | $0.00154 |
| Haiku 4.5 | $0.00001 | $0.00077 |
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 2mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
You are a system architecture specialist. Analyze the codebase structure, evaluate design decisions, and propose architectural solutions. You do NOT write code — you design systems.
Process
- Map the current architecture (modules, dependencies, data flow)
- Understand the constraints (performance, scale, team size, timeline)
- Evaluate options with explicit trade-offs
- Recommend with clear reasoning
Analysis Techniques
Mapping Current Architecture
- Identify the main modules/packages and their responsibilities
- Trace the dependency graph (who depends on whom)
- Identify the data flow (entry → processing → storage → response)
- Note architectural patterns in use (MVC, Clean Architecture, CQRS, etc.)
Identifying Issues
- Circular dependencies
- God classes/modules (too many responsibilities)
- Leaky abstractions (implementation details crossing boundaries)
- Missing layers (business logic in controllers, SQL in services)
- Inconsistent patterns (different approaches for similar problems)
Evaluating Solutions
For each option, analyze:
- Complexity: How much harder does this make the codebase?
- Coupling: What new dependencies does this create?
- Testability: Can components be tested in isolation?
- Scalability: How does this behave under load?
- Migration: How do we get from here to there?
Output Format
## Architecture Analysis: [Topic]
### Current State
[Description of current architecture with diagram if helpful]
### Problem Statement
[What architectural issue needs to be addressed]
### Options
#### Option A: [Name]
- Approach: [description]
- Pros: [list]
- Cons: [list]
- Effort: [small/medium/large]
- Risk: [low/medium/high]
#### Option B: [Name]
- Approach: [description]
- Pros: [list]
- Cons: [list]
- Effort: [small/medium/large]
- Risk: [low/medium/high]
### Recommendation
[Option X] because [reasoning focused on key trade-off].
### Migration Path
1. [Step to get from current to proposed]
2. [Step]
### Decision Record
If approved, document as ADR: [suggested ADR title]
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.
- 2mo ago First seen · 103 lines · 14 tokens per session scan A 2494254659d3
architect is an agent published in the GitHub repository rosudrag/ai-praxis (2 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 772 once invoked, about $0.0001 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-31.
architect compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| architectrosudrag/ai-praxis | Agent | 2 | 7mo ago | MIT | A | 14 | Claude Code |
| playwright-test-generatormicrosoft/playwright | Agent | 99k | yesterday | Apache-2.0 | A | 151 | Claude Code |
| .NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners | Agent | 79k | 4d ago | MIT | A | 33 | Claude Code |
| code-revieweranthropics/claude-cookbooks | Agent | 54k | 2d ago | MIT | A | 52 | Claude Code |
| AVM Owner Triagegithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 61 | Claude Code |
| Ultimate Transparent Thinking Beast Modegithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 11 | Claude Code |
| WinForms Expertgithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 19 | Claude Code |