Plano is a proxy server and data plane that handles shared infrastructure for applications built with AI agents, including agent routing, orchestration, model selection, traces, metrics, and guardrails. Developers use it to connect agents and language models to production applications without embedding this middleware in each application. The catalogue entries provide skills and instructions for operating or developing with Plano.
Borrowing it
Nothing to install: this file belongs to katanemo/plano. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/katanemo/plano/main/.claude/skills/pr/SKILL.mdgit clone --depth 1 https://github.com/katanemo/planoWrote 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/skills/katanemo/plano/pr)<a href="https://agentmods.dev/skills/katanemo/plano/pr"><img src="https://agentmods.dev/badge/skills/katanemo/plano/pr/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/skills/katanemo/plano/pr"><img src="https://agentmods.dev/badge/skills/katanemo/plano/pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00016 | $0.00222 |
| Opus 5.5 | $0.00006 | $0.00089 |
| Sonnet 5.5 | $0.00003 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
pr 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 2mo 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
Create a pull request for the current changes:
- Determine the GitHub username via
gh api user --jq .login. If the login isadilhafeez, useadilinstead. - Create a feature branch using format
<username>/<feature_name>— infer the feature name from the changes - Run
cd crates && cargo fmt --all -- --checkandcd crates && cargo clippy --locked --all-targets --all-features -- -D warningsto verify Rust code is clean - Commit all changes with a short, concise commit message (one line, no Co-Authored-By)
- Push the branch and create a PR targeting
main
Keep the PR title short (under 70 chars). Include a brief summary in the body. Never include a "Test plan" section or any "Generated with Claude Code" attribution.
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.
- 2mo ago First seen · 17 lines · 16 tokens per session scan A 191f05c57b0b
pr is a skill published in the GitHub repository katanemo/plano (7,100 stars, last pushed 5d ago), licensed Apache-2.0. It adds 16 tokens to every session and 222 once invoked, about $0.0001 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-30.
Other skills, from other repositories
project-graveyard
Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions…
commit-archaeologist
Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion files, and likely intent. Use when the user asks "why does this code exist", "who wrote this function and why", or to "explain the history of this function" before a rewrite…
scope-creep-detector
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad pull requests, changes that grew beyond a fix, dependency additions, public API renames, config or CI edits, oversized hunks, and formatting-only files. Use when the user asks whether a change grew beyond the fix, a PR is too…
contextual-commit
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
conventional-commit
Rules for writing Conventional Commits messages in this project. MUST be invoked every time a commit is created.
configure-workspaces
Propose and generate workspace configuration files (.humanlayer/workspace.json and .humanlayer/workspace.local.json) for a repository.