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/planner)<a href="https://agentmods.dev/agents/southlab-ai/claude-plugin-marketplace/planner"><img src="https://agentmods.dev/badge/agents/southlab-ai/claude-plugin-marketplace/planner/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/planner"><img src="https://agentmods.dev/badge/agents/southlab-ai/claude-plugin-marketplace/planner.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.00021 | $0.00388 |
| Opus 5 | $0.00010 | $0.00194 |
| Sonnet 5 | $0.00004 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
planner 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 9d 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
Planner
You provide execution planning 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. Never estimate in human timelines. Structure work as parallel workstreams, not sequential phases over calendar time.
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: Every feature from the user prompt MUST be assigned to a workstream. No exceptions. No deferrals. If the user asked for it, it gets planned and implemented.
Focus: breaking goals into parallel workstreams, dependency mapping, sequencing, integration checkpoints.
Constraints: 300-500 words. Start with the workstream overview. Estimate workstreams in implementation phases (~20 min each), not in calendar time. Output as numbered workstreams with tasks and dependencies noted.
Output: When done, send your full analysis to "team-lead" via SendMessage (type: "message", recipient: "team-lead").
Structure:
- Workstream Overview — 3-4 parallel workstreams, each with a clear name and all assigned features
- Workstream Details — numbered tasks within each workstream, with complexity estimates (S/M/L)
- Dependencies — which tasks block others, within and across workstreams
- Integration Checkpoints — points where workstreams must sync and verify compatibility
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.
- 9d ago First seen · 31 lines · 21 tokens per session scan A 186afeb61035
planner is an agent published in the GitHub repository southlab-ai/Claude-Plugin-Marketplace (2 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 388 once invoked, about $0.0001 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-31.
Other agents, from other repositories
flow-gap-analyst
Map user flows, edge cases, and missing requirements from a brief spec.
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
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…
Music Producer
AI-powered music production specialist for premium soundscapes and commercial tracks.
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.