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.
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 skills add katanemo/plano --skill plano-deployment-securitygit 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/plano-deployment-security)<a href="https://agentmods.dev/skills/katanemo/plano/plano-deployment-security"><img src="https://agentmods.dev/badge/skills/katanemo/plano/plano-deployment-security/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/plano-deployment-security"><img src="https://agentmods.dev/badge/skills/katanemo/plano/plano-deployment-security.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.00032 | $0.00209 |
| Opus 5.5 | $0.00013 | $0.00084 |
| Sonnet 5.5 | $0.00006 | $0.00042 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
plano-deployment-security 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.
What it actually says
Plano Deployment and Security
Use this skill to harden production deployments and reduce runtime surprises.
When To Use
- "Fix unreachable agents in Docker"
- "Configure persistent conversation state"
- "Add readiness and health checks"
- "Prepare production deployment checklist"
Apply These Rules
deploy-dockerdeploy-statedeploy-health
Execution Checklist
- Use
host.docker.internalfor host-side services from inside Plano container. - Prefer PostgreSQL state storage for production multi-turn workloads.
- Verify
/healthzbefore traffic or CI assertions. - Ensure secrets remain environment-based, never hardcoded.
- Return deployment checks with failure-mode diagnostics.
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 · 34 lines · 32 tokens per session scan A a4450f85d5dc
plano-deployment-security is a skill published in the GitHub repository katanemo/plano (7,099 stars, last pushed 3d ago), licensed Apache-2.0. It adds 32 tokens to every session and 209 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
k8s-pod-escape
Kubernetes pod escape to node — privileged container abuse, hostPath mount escape, hostPID/hostIPC, capability misuse (SYSADMIN, SYSPTRACE), runC CVE chains. Pivots from RCE-in-pod to full node compromise.
k8s-pivot
Kubernetes attack playbook — service-account token theft, RBAC abuse, pod escape, hostPath mount abuse, kube-api-server pivoting.
container-cve
High-impact container-runtime CVE catalog — runC Leaky Vessels (CVE-2024-21626/-23651/-23652/-23653), CVE-2022-0185 (FUSE/legacy-fs), CVE-2019-5736 (runC binary replace), CRI-O Dirty COW analogs, Kubernetes API server CVE-2019-11247 (custom-resource RBAC bypass). Fingerprint → match → exploit.
container-overview
Container / Kubernetes attack category — pod escape, RBAC abuse, runtime CVE exploitation, socket-mount escape. Routing skill: identify the surface (pod-internal RCE vs API-level vs build-pipeline), then load the matching sub-skill.
neuron-laravel-integration
Integrate Neuron AI agents into a Laravel 13 app the framework-native way — setup checklist (App\Neuron layout, config/services.php keys, one migration, NeuronServiceProvider, bootstrap/app.php exception mapping, neuron:evaluate), container-built agents bound per thread with for(), thread authorization, JSON and…
neuron-symfony-integration
Integrate Neuron AI agents into a Symfony 8 app, from packages, env keys, a Doctrine migration for the Neuron tables and services.yaml wiring to a shared agent bound per request with for(), a thread voter, JSON and AG-UI (CopilotKit) or useChat streaming with StreamedResponse, reload with pending approvals, Messenger…