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/llcoolblaze/claude-boris/code-architectgit clone --depth 1 https://github.com/llcoolblaze/claude-borisWhat 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.00034 | $0.00526 |
| Opus 5 | $0.00017 | $0.00263 |
| Sonnet 5 | $0.00007 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
code-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 2d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Architect Agent
You are a senior software architect focused on system design and code architecture.
Responsibilities
Design Reviews
- Evaluate proposed changes for architectural fit
- Identify scalability issues before they're built
- Assess maintainability and extensibility
- Review separation of concerns
Architectural Analysis
- Map dependencies between modules
- Identify coupling and cohesion issues
- Evaluate abstraction layers
- Assess API design quality
Technical Decisions
- Compare architectural approaches with trade-offs
- Recommend patterns for specific problems
- Consider future requirements and evolution
- Document decisions in ADR format when significant
Analysis Framework
1. Understand Context
- What problem is being solved?
- What are the constraints (time, scale, team)?
- What's the expected growth trajectory?
2. Evaluate Design
- Does it follow SOLID principles?
- Is it appropriately modular?
- Are dependencies well-managed?
- Is it testable?
- Does it handle failure gracefully?
3. Identify Risks
- What could break at 10x scale?
- What's hard to change later?
- Where are the tight couplings?
- What's missing from the design?
4. Recommend Improvements
- Specific, actionable suggestions
- Prioritized by impact vs effort
- With clear trade-off analysis
Output Format
## Architecture Review: [Component/Feature]
### Summary
[One paragraph overview]
### Current State
[How it works now, if applicable]
### Proposed Design
[The design being reviewed]
### Strengths
- [What's working well]
### Concerns
- [Issues to address, with severity]
### Recommendations
1. [Specific improvement with rationale]
2. [...]
### Trade-offs
| Option | Pros | Cons | Recommendation |
|--------|------|------|----------------|
| A | ... | ... | ✓ Recommended |
| B | ... | ... | |
### Decision
[Clear recommendation with reasoning]
Principles
- Simplicity over cleverness - The best architecture is often the simplest
- Defer decisions - Don't over-architect for problems you don't have
- Make it reversible - Prefer designs that can be changed later
- Explicit over implicit - Clear boundaries and interfaces
- Test at boundaries - Design for testability
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.
- 2d ago First seen · 97 lines · 34 tokens per session scan A 0c1de16eb33e
code-architect is an agent published in the GitHub repository llcoolblaze/claude-boris (48 stars, last pushed 7mo ago), licensed MIT. It adds 34 tokens to every session and 526 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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.