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/lifangda/claude-pluginsWrote 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/lifangda/claude-plugins/code-architect)<a href="https://agentmods.dev/agents/lifangda/claude-plugins/code-architect"><img src="https://agentmods.dev/badge/agents/lifangda/claude-plugins/code-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/lifangda/claude-plugins/code-architect"><img src="https://agentmods.dev/badge/agents/lifangda/claude-plugins/code-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.00146 | $0.00526 |
| Opus 5.5 | $0.00058 | $0.00210 |
| Sonnet 5.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 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.
This is a copy
100% identical to code-architect — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo 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 11mo ago), licensed MIT. It adds 146 tokens to every session and 526 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to code-architect, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…