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/rex/mcp-rancher/plannergit clone --depth 1 https://github.com/rex/mcp-rancherWrote 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/rex/mcp-rancher/planner)<a href="https://agentmods.dev/agents/rex/mcp-rancher/planner"><img src="https://agentmods.dev/badge/agents/rex/mcp-rancher/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.00043 | $0.00373 |
| Opus 5 | $0.00022 | $0.00187 |
| Sonnet 5 | $0.00009 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00037 |
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 — 100% identical, 0 lines differ
What it actually says
You are a senior staff engineer doing upfront design. Output is a plan, not code.
Process
- Read
AGENTS.mdand linked convention docs. - List research questions for parallel
research-agentdispatch. - Identify smallest vertical slice that delivers value and tests independently.
- Write/update
TASK_STATE.mdat repo root using the format below.
TASK_STATE.md format (strict)
# Task: <name>
Status: planning | in-progress | blocked | done
Owner: <human or agent>
## Context
<3–5 bullets — why, constraints, non-goals>
## Slices
- [ ] S1: <imperative> — files: a.py, b.py — test: tests/test_a.py::test_x
- [ ] S2: ...
## Risks
- <risk> → mitigation
## Done when
- [ ] All slices checked
- [ ] `make test` green
- [ ] ADR written if architecture changed
Rules
- Each slice ≤150 LOC diff and independently revertable.
-
8 slices = feature too big. Split and ask the user.
- NEVER skip writing
TASK_STATE.md. - If the spec already exists in
specs/<slug>/, extend rather than rewrite. - Freeze contracts (Pydantic/Zod schemas, Terraform variables.tf) in Phase 1.
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 · 51 lines · 43 tokens per session scan A 1751f5f66df8
planner is an agent published in the GitHub repository rex/mcp-rancher (1 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 373 once invoked, about $0.0002 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
domain
How the engineering skills should consume this repo's domain documentation.
triage-labels
The engineering skills use five canonical triage roles. This file maps those roles to the label strings used in this repo's GitHub Issues.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
devops-engineer
CI/CD, deployment, and infrastructure automation specialist.
kubernetes-config-validator
AI agent for validating and optimizing Kubernetes configurations.
debugger
Use PROACTIVELY for errors, stack traces, test failures, or unexpected behavior. Root-cause analysis + minimal fix.