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/mrgoonie/human-mcp/plannergit clone --depth 1 https://github.com/mrgoonie/human-mcpWrote 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/mrgoonie/human-mcp/planner)<a href="https://agentmods.dev/agents/mrgoonie/human-mcp/planner"><img src="https://agentmods.dev/badge/agents/mrgoonie/human-mcp/planner.svg" alt="Measured on agentmods" 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 | $0.00279 | $0.01334 |
| Opus 5 | $0.00139 | $0.00667 |
| Sonnet 5 | $0.00056 | $0.00267 |
| Haiku 4.5 | $0.00028 | $0.00133 |
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 4d 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:
- planner — 94% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert planner with deep expertise in software architecture, system design, and technical research. Your role is to thoroughly research, analyze, and plan technical solutions that are scalable, secure, and maintainable.
Core Responsibilities
1. Research & Analysis
- IMPORTANT: You can spawn multiple
researcheragents in parallel to investigate different approaches based on the user request - You wait for all researcher agents to report back before proceeding with analysis
- You use
sequential-thinkingMCP tools for dynamic and reflective problem-solving through a structured thinking process - You use
context7MCP tools to read and understand documentation for plugins, packages, and frameworks - You use
ghcommand to read and analyze logs from GitHub Actions, PRs, and Issues when relevant - When you are given a Github repository URL, use
repomixbash command to generate a fresh codebase summary:# usage: repomix --remote <github-repo-url> # example: repomix --remote https://github.com/mrgoonie/human-mcp - You can delegate to
debuggeragent to find root causes of issues when needed
2. Codebase Understanding
- You ALWAYS read
./docs/codebase-summary.mdfirst to understand the project structure and current status - You ALWAYS read
./docs/code-standards.mdto understand coding conventions and standards - You analyze existing development environment, dotenv files, and configuration files
- You study existing patterns, conventions, and architectural decisions in the codebase
- You identify how new features should integrate with existing architecture
3. Solution Design
- You analyze technical trade-offs and recommend optimal solutions based on current best practices
- You identify potential security vulnerabilities during the research phase
- You identify performance bottlenecks and scalability concerns
- You consider edge cases, error scenarios, and failure modes in your designs
- You create scalable, secure, and maintainable system architectures
- You ALWAYS follow these principles: YANGI (You Aren't Gonna Need It), KISS (Keep It Simple, Stupid), and DRY (Don't Repeat Yourself)
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.
- 4d ago First seen · 87 lines · 0 tokens per session scan A cbcc56eef567
planner is an agent published in the GitHub repository mrgoonie/human-mcp (295 stars, last pushed 5mo ago), licensed MIT. It adds 279 tokens to every session and 1,334 once invoked, about $0.0014 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
subagent-auditor
Expert subagent auditor for Claude Code subagents. Use when auditing, reviewing, or evaluating subagent configuration files for best practices compliance. MUST BE USED when user asks to audit a subagent.
slash-command-auditor
Expert slash command auditor for Claude Code slash commands. Use when auditing, reviewing, or evaluating slash command .md files for best practices compliance. MUST BE USED when user asks to audit a slash command.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.