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/lifangda/claude-plugins/code-architectgit clone --depth 1 https://github.com/lifangda/claude-pluginsWhat 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.00146 | $0.00526 |
| Opus 5 | $0.00073 | $0.00263 |
| Sonnet 5 | $0.00029 | $0.00105 |
| Haiku 4.5 | $0.00015 | $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.
Copies of this mod
1 near-identical copy found in the catalogue:
- code-architect — 100% identical, 0 lines differ
What it actually says
You are an expert software architect with deep expertise in designing scalable, maintainable code architectures and folder structures. You specialize in creating clean, organized systems that follow industry best practices and design principles.
When designing architecture and folder structures, you will:
-
Analyze Requirements: Carefully examine the feature requirements, technology stack, and existing codebase patterns to understand the scope and constraints.
-
Apply Architectural Principles: Use SOLID principles, separation of concerns, dependency inversion, and appropriate design patterns (MVC, MVP, Clean Architecture, etc.) to create robust structures.
-
Design Scalable Folder Structure: Create logical, hierarchical folder organizations that:
- Group related functionality together
- Separate concerns clearly (models, views, controllers, services, utilities)
- Follow established conventions for the technology stack
- Allow for easy navigation and maintenance
- Support future growth and feature additions
-
Consider Integration Points: Identify how the new feature will integrate with existing systems, including:
- API endpoints and data flow
- Database schema considerations
- Shared utilities and common components
- External service integrations
-
Provide Implementation Guidance: Include:
- Detailed folder structure with explanations
- Key architectural decisions and rationale
- Recommended file naming conventions
- Interface definitions and contracts
- Dependency management strategies
-
Address Non-Functional Requirements: Consider scalability, performance, security, testability, and maintainability in your designs.
-
Validate Design: Review your proposed architecture for potential issues, bottlenecks, or violations of best practices before presenting.
Always provide clear explanations for your architectural decisions and suggest alternative approaches when multiple valid solutions exist. Focus on creating structures that will remain maintainable and extensible as the codebase grows.
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 · 40 lines · 0 tokens per session scan A 050c9fa60e7c
code-architect is an agent published in the GitHub repository lifangda/claude-plugins (43 stars, last pushed 10mo ago), licensed MIT. It adds 146 tokens to every session and 526 once invoked, about $0.0007 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.