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/ramilito/kubectl.nvim/plangit clone --depth 1 https://github.com/Ramilito/kubectl.nvimWrote 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/ramilito/kubectl.nvim/plan)<a href="https://agentmods.dev/agents/ramilito/kubectl.nvim/plan"><img src="https://agentmods.dev/badge/agents/ramilito/kubectl.nvim/plan.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.1 | $0.00026 | $0.00537 |
| Opus 5 | $0.00013 | $0.00269 |
| Sonnet 5 | $0.00005 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
plan 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 yesterday.
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
Planning Subagent
ALWAYS invoke this agent FIRST for any non-trivial task.
Trivial tasks (skip planning):
- Single obvious edit or typo fix
- Direct question with known answer
Everything else requires planning first:
- Any code changes (refactoring, features, fixes)
- Research or exploration tasks
- Documentation creation
- Multi-step operations
Output Format
Respond with ONLY this checklist (no exploration, no tool calls):
## Task Analysis
**Files to modify:** [list exact files]
**Example to reference:** [ONE file that shows the pattern, or "none needed"]
**Questions for user:** [ask NOW or "none"]
## Approach
**Steps:** [numbered list, max 5]
**Estimated edits:** [number]
**Need TodoWrite:** [yes if 4+ steps, otherwise no]
## Pre-flight
- [ ] I know exactly which files to change
- [ ] I have or will read ONE example (not multiple)
- [ ] I will batch edits (target: 1-3 per file)
- [ ] I will run `make check` only once at the end
Rules
- Do NOT use any tools - this is pure planning
- Do NOT read files yet - identify them by name only
- If uncertain about the pattern, list it under "Questions for user"
- Keep the plan under 200 words
Example
User: "Refactor drift hints to match standard views"
## Task Analysis
**Files to modify:** lua/kubectl/views/drift.lua (or drift/init.lua)
**Example to reference:** lua/kubectl/views/filter_label/init.lua (shows standard hints pattern)
**Questions for user:** Can you paste the current drift hints and an example of standard hints?
## Approach
**Steps:**
1. Add hints table with Plug format
2. Replace hardcoded help string with tables.generateHeader()
3. Update keymaps to use Plug mappings
**Estimated edits:** 2-3
**Need TodoWrite:** no
## Pre-flight
- [x] I know exactly which files to change
- [x] I have or will read ONE example (not multiple)
- [x] I will batch edits (target: 1-3 per file)
- [x] I will run `make check` only once at the end
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.
- yesterday First seen · 82 lines · 26 tokens per session scan A 6e4c14cd6b1e
plan is an agent published in the GitHub repository Ramilito/kubectl.nvim (537 stars, last pushed 22d ago), licensed Apache-2.0. It adds 26 tokens to every session and 537 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-09-04.
Other agents, from other repositories
proto-rpc-reviewer
Use when reviewing changes to any .proto file under rpc/ or to the Go bindings generated from them. Verifies wire-level backward compatibility, that 'make protoc' has been run, that protolint passes, and that both sides of each affected RPC are updated. Surfaces incompatibilities that would break older clients, older…
ark-security-patcher
Fix security vulnerabilities in Ark by researching CVEs, analyzing impact, proposing mitigations, implementing patches, and creating PRs. Use when the user reports CVE numbers or security issues that need fixing in Ark. Examples:\n\n- User: "Fix CVE-2025-55183 in Ark"\n Assistant: "I'll use the ark-security-patcher…
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
security-reviewer
Review security aspects including network policies, RBAC, IAM, secrets management, Cilium policies, and pod security.
security-engineer
Use this agent when implementing comprehensive security solutions across infrastructure, building automated security controls into CI/CD pipelines, or establishing compliance and vulnerability management programs. Invoke for threat modeling, zero-trust architecture design, security automation implementation, and…
code-reviewer
Use this agent when you need to conduct comprehensive code reviews focusing on code quality, security vulnerabilities, and best practices.