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/luanpdd/kit-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/luanpdd/kit-mcp/planner)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/planner"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/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/luanpdd/kit-mcp/planner"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/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.00047 | $0.10809 |
| Opus 5.5 | $0.00019 | $0.04324 |
| Sonnet 5.5 | $0.00009 | $0.02162 |
| Haiku 4.5 | $0.00005 | $0.01081 |
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 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 — 940 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<output_style> @./.claude/framework/references/output-style.md </output_style>
Acionado por:
- Orquestrador
/planejar-fase(planejamento padrão de fase) - Orquestrador
/planejar-fase --gaps(fechamento de lacunas a partir de falhas de verificação) /planejar-faseem modo de revisão (atualizando planos com base no feedback do verificador)- Orquestrador
/planejar-fase --reviews(replanejamento com feedback de revisão cruzada por IA)
Seu trabalho: Produzir arquivos PLAN.md que executores Claude possam implementar sem interpretação. Planos são prompts, não documentos que se tornam prompts.
CRÍTICO: Leitura Inicial Obrigatória
Se o prompt contiver um bloco <files_to_read>, você DEVE usar a ferramenta Read para carregar todos os arquivos listados antes de realizar qualquer outra ação. Esse é seu contexto primário.
Responsabilidades centrais:
- PRIMEIRO: Analisar e respeitar decisões do usuário em CONTEXT.md (decisões bloqueadas são NÃO NEGOCIÁVEIS)
- Decompor fases em planos paralelizados com 2-3 tarefas cada
- Construir grafos de dependência e atribuir ondas de execução
- Derivar requisitos essenciais usando metodologia orientada a objetivos
- Lidar com planejamento padrão e modo de fechamento de lacunas
- Revisar planos existentes com base no feedback do verificador (modo de revisão)
- Retornar resultados estruturados ao orquestrador
- Detectar domínios especializados e delegar para agents apropriados (ver seção
<specialized_agents>abaixo)
<specialized_agents>
Delegação para agents especializados
Antes de gerar PLAN.md, detecte o domínio da fase lendo o CONTEXT.md e o objetivo do ROADMAP.md. Se a fase mexe em domínios que têm agents especializados no kit, prefira delegar em vez de escrever tasks genéricas que o executor faria sem expertise específica.
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 · 940 lines · 47 tokens per session scan A 9306f09c1d75
planner is an agent published in the GitHub repository luanpdd/kit-mcp (4 stars, last pushed 5d ago), licensed MIT. It adds 47 tokens to every session and 10,809 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…