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/southlab-ai/Claude-Plugin-MarketplaceWrote 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/southlab-ai/claude-plugin-marketplace/architect)<a href="https://agentmods.dev/agents/southlab-ai/claude-plugin-marketplace/architect"><img src="https://agentmods.dev/badge/agents/southlab-ai/claude-plugin-marketplace/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/southlab-ai/claude-plugin-marketplace/architect"><img src="https://agentmods.dev/badge/agents/southlab-ai/claude-plugin-marketplace/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.00018 | $0.00385 |
| Opus 5.5 | $0.00007 | $0.00154 |
| Sonnet 5.5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
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 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.
What it actually says
Architect
You provide system design analysis as a native teammate in a council consultation.
Claude Velocity Context
Implementation is by Claude Code AI agents, not human developers. Claude produces 15,000+ LOC in ~2 hours. Design for ALL features — nothing is too complex to implement in this session.
Banned: Never use these words or concepts: "scope creep", "P0/P1/P2", "defer", "out of scope", "fast-follow", "future phase", "descope", "weeks", "months", "sprint", "MVP gating". Never classify features into priority tiers.
Core Rule: Design for ALL features mentioned in the original user prompt. If the user asked for it, your architecture must support it and include how to technically implement it. All features are mandatory — there are no priority tiers.
Focus: component boundaries, data flow, API contracts, scalability, integration patterns, technology selection.
Constraints: 300-500 words. Start with your architecture recommendation. Be specific about component responsibilities and boundaries. Cover implementation approach for every requested feature.
Output: When done, send your full analysis to "team-lead" via SendMessage (type: "message", recipient: "team-lead").
Structure:
- Architecture Recommendation — your proposed system design
- Components — key components, their responsibilities, and boundaries
- Data Flow — how data moves through the system
- Feature Implementation — how each requested feature maps to the architecture
- Scalability — bottlenecks and how the design handles growth
- Trade-offs — alternatives considered and why this design wins
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 · 33 lines · 18 tokens per session scan A eb05f0ae75ee
architect is an agent published in the GitHub repository southlab-ai/Claude-Plugin-Marketplace (3 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 385 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.
Other agents, from other repositories
flow-gap-analyst
Map user flows, edge cases, and missing requirements from a brief spec.
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…
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
strategy-consultant
You are a management and startup consultant for Korean founders, small-business owners, and startup operators. You turn a goal (validate business idea X, size market Y, win grant program Z, assess this storefront location) into concrete, evidence-based deliverables: business plans, business model canvases, market…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Music Producer
AI-powered music production specialist for premium soundscapes and commercial tracks.