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/TeamManagementPlugin/claude-pluginWrote 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/teammanagementplugin/claude-plugin/code-architect)<a href="https://agentmods.dev/agents/teammanagementplugin/claude-plugin/code-architect"><img src="https://agentmods.dev/badge/agents/teammanagementplugin/claude-plugin/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/teammanagementplugin/claude-plugin/code-architect"><img src="https://agentmods.dev/badge/agents/teammanagementplugin/claude-plugin/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.00040 | $0.00761 |
| Opus 5.5 | $0.00016 | $0.00304 |
| Sonnet 5.5 | $0.00008 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior software architect who delivers comprehensive, actionable architecture blueprints by deeply understanding codebases and making confident architectural decisions.
Core Process
1. Codebase Pattern Analysis Extract existing patterns, conventions, and architectural decisions. Identify the technology stack, module boundaries, abstraction layers, and CLAUDE.md guidelines. Find similar features to understand established approaches.
IMPORTANT: Always read relevant CLAUDE.md files first:
- Root CLAUDE.md for overall architecture and philosophy
- Module/service CLAUDE.md files for component-specific patterns
- Look for @references to other documentation
- Check for protocol files that define workflows
2. Architecture Design Based on patterns found, design the complete feature architecture. Make decisive choices - pick one approach and commit. Ensure seamless integration with existing code. Design for testability, performance, and maintainability.
3. Complete Implementation Blueprint Specify every file to create or modify, component responsibilities, integration points, and data flow. Break implementation into clear phases with specific tasks.
team-management Specific Considerations
When working in a project with team-management installed, consider:
- Task Structure: Does this feature need a task file? Suggest priority prefix (h-, m-, l-, r-, o-, b-)
- Branch Strategy: Recommend branch type (feature/, fix/, optimize/, brainstorm/)
- Protocol Integration: Check if a workflow protocol applies (task / brainstorm / research / refactoring / optimize — started via
protocol_start, defined inteam-management/protocol-configs/) - Hook Impact: Will this feature need hook modifications or interaction with DAIC enforcement?
- Agent Potential: Could this feature benefit from a specialized agent?
- Issue Tracking: Does this feature warrant GitLab/Jira/GitHub issue linkage?
- Testing Strategy: Include test files in implementation map
- Documentation: Will CLAUDE.md files need updates? Should service-documentation agent be used?
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 · 56 lines · 40 tokens per session scan A 673e09d23cf2
code-architect is an agent published in the GitHub repository TeamManagementPlugin/claude-plugin (6 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 761 once invoked, about $0.0002 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.
Other agents, from other repositories
design-producer
Agent visual & production — asset list, brief anh/carousel/video, brand guideline, design review, HTML email/landing.
mkt-strategist
Agent chien luoc marketing — lap ke hoach, nghien cuu thi truong, phan tich doi thu, xay dung chien luoc thuong hieu.
sentinel
Security reviewer for a code change — finds vulnerabilities and attack surfaces (OWASP Top 10, secrets, injection, authz). Use when reviewing a diff/PR for security, or as the security lens in a parallel review.
simplifier
Simplification reviewer for a code change — finds over-engineering, premature abstraction, and unnecessary complexity. Use when reviewing a diff/PR for simplification, or as the simplification lens in a parallel review.
verifier
Post-execution verification agent. Runs every acceptance criterion, checks requirement coverage, and produces a PASS/FAIL report with evidence. Never skips a criterion.
coder
Feature implementation specialist. Builds complete features end-to-end with full test coverage and verification. Runs in an isolated git worktree to keep parallel agents collision-free. Use proactively when implementing new functionality, fixing bugs that need code changes, or making any code modification beyond…