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 Neeeophytee/agent-stylebooks --skill kubernetes-docsgit clone --depth 1 https://github.com/Neeeophytee/agent-stylebooksWrote 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/neeeophytee/agent-stylebooks/kubernetes-docs)<a href="https://agentmods.dev/skills/neeeophytee/agent-stylebooks/kubernetes-docs"><img src="https://agentmods.dev/badge/skills/neeeophytee/agent-stylebooks/kubernetes-docs.svg" alt="Measured on agentmods" 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.00058 | $0.00683 |
| Opus 5 | $0.00029 | $0.00342 |
| Sonnet 5 | $0.00012 | $0.00137 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
kubernetes-docs 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 8d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes docs
Produce direct, version-aware cloud-native documentation that readers can apply without guessing which object, namespace, context, or feature state is involved.
Preserve operational accuracy
- Keep resource kinds, API versions, field names, commands, flags, YAML, output, feature states, and version boundaries exact.
- Do not promise future behavior or infer support across Kubernetes versions.
- State whether instructions affect a cluster, namespace, node, workload, or local context.
- Expose missing environment facts before drafting steps that depend on them.
Choose the content shape
- Concept: explain a model, component, or relationship without turning it into a task.
- Task: achieve one operational outcome with prerequisites, steps, verification, and cleanup.
- Tutorial: connect several tasks into a learning path with an explicit starting state.
- Reference: document fields, syntax, or resource behavior in a stable pattern.
Keep conceptual context short in a task. Link or separate deep architecture when it is not needed to execute safely.
Write precisely
- Address the reader as
you; avoid ambiguouswe. - Use present tense for behavior and active voice when the actor matters.
- Name the API object or component rather than using an unclear pronoun.
- Use
Kubernetesfor the system and exact resource-kind capitalization when referring to an API kind. Use ordinary lowercase words for general concepts. - Define specialized terms and abbreviations where the intended audience first needs them.
- Prefer literal language that translates well. Avoid idioms and insider shorthand.
- Tie claims such as deprecated, beta, stable, or removed to a version or feature state.
Write operational steps
- State the required cluster access, namespace, context, tools, and starting resources.
- Start each step with an imperative verb.
- Use angle-bracket placeholders in commands and explain every placeholder.
- Put filenames, paths, commands, flags, fields, and literal values in backticks.
- Show representative output only when the reader needs it to verify or diagnose.
- Include a success check and cleanup for resources created by a tutorial.
- Place cautions before commands that delete, expose, or disrupt resources.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 68 lines · 58 tokens per session scan A 19ea4dc60649
kubernetes-docs is a skill published in the GitHub repository Neeeophytee/agent-stylebooks (58 stars, last pushed 15d ago), licensed MIT. It adds 58 tokens to every session and 683 once invoked, about $0.0003 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-30.
Other skills, from other repositories
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
gcloud-usage
This skill should be used when user asks about "GCloud logs", "Cloud Logging queries", "Google Cloud metrics", "GCP observability", "trace analysis", or "debugging production issues on GCP".
ultralytics-platform
This skill should be used when user asks to "upload my model to Ultralytics Platform", "push this run to the platform", "upload a dataset to platform", "download a dataset from platform", "search platform datasets", "start cloud training", "train on platform GPUs", "export a model on platform", "deploy a model…
azure-usage
This skill should be used when user asks to "query Azure resources", "list storage accounts", "manage Key Vault secrets", "work with Cosmos DB", "check AKS clusters", "use Azure MCP", or interact with any Azure service.
setup
This skill should be used when user encounters "Azure MCP error", "Azure authentication failed", "az login required", "Azure CLI not found", or needs help configuring Azure MCP integration.
lov-deploy-to-vercel
A deployment workflow for publishing Vite, Next.js, Create React App, or static frontend projects on Vercel, a hosting service for web applications. It can also connect a custom domain and configure Cloudflare DNS records.