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 paruff/uFawkesAI --skill k8s-design-validationgit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/k8s-design-validation)<a href="https://agentmods.dev/skills/paruff/ufawkesai/k8s-design-validation"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/k8s-design-validation/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/paruff/ufawkesai/k8s-design-validation"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/k8s-design-validation.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.00570 |
| Opus 5 | $0.00015 | $0.00285 |
| Sonnet 5 | $0.00006 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
k8s-design-validation 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 10d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Kubernetes Design Validation
Load trigger:
"load k8s-design-validation skill"> DORA: Cap 1 (AI Policy) Token cost: Low
Purpose
Validate Kubernetes-related design decisions.
Responsibilities
- Validate resource requirements in design
- Validate deployment patterns
- Validate network design
- Validate secret usage approach
Inputs
design.mdarchitecture.json
Outputs
k8s-design.json
Validation Rules
Resource Design
- CPU requests/limits specified per component
- Memory requests/limits specified per component
- Storage requirements specified (if applicable)
- Horizontal scaling approach defined
Deployment Patterns
- Deployment strategy chosen (RollingUpdate, Recreate)
- Replica count specified
- Pod disruption budgets defined (if needed)
- Init containers defined (if needed)
Network Design
- Service types defined (ClusterIP, NodePort, LoadBalancer)
- Ingress rules defined
- Network policies defined
- DNS strategy defined
Secret Management
- Secret storage approach chosen (native, Vault, ExternalSecrets)
- Secret rotation strategy defined
- Secret access pattern defined
- Encryption at rest approach defined
Storage Design
- Persistent volume claims defined (if needed)
- Storage classes specified
- Backup strategy defined (if needed)
Design Patterns
| Pattern | Use When |
|---|---|
| Deployment | Stateless workloads |
| StatefulSet | Stateful workloads (databases, queues) |
| DaemonSet | Node-level agents (logging, monitoring) |
| Job/CronJob | Batch or scheduled workloads |
Output Format
{
"skill": "k8s-design-validation",
"status": "pass | fail",
"checks": [
{
"area": "Resource design",
"status": "pass | fail | na",
"details": "Description"
}
],
"recommendations": ["Consider adding PodDisruptionBudget for production"],
"violations": []
}
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.
- 10d ago First seen · 104 lines · 31 tokens per session scan A f9809fe5632c
k8s-design-validation is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 18d ago), licensed MIT. It adds 31 tokens to every session and 570 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 skills, from other repositories
infrastructure-docker
Container build and compose assets for the research template. Use when reproducing CI or cloud environments with Docker, following docs/CLOUDDEPLOY.md, or wiring Ollama sidecars via docker-compose.
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".
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
cloudron-app-packaging
Official Cloudron app packaging skill - Dockerfile patterns, manifest, addons, build methods.
devops-infrastructure
Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup. Use when writing Dockerfiles, configuring GitHub Actions, planning deployments, setting up monitoring, or when asked about containers, pipelines, Terraform, or production infrastructure.
qdrant-deployment-options
Guides Qdrant deployment selection. Use when someone asks 'how to deploy Qdrant', 'Docker vs Cloud', 'local mode', 'embedded Qdrant', 'Qdrant EDGE', 'which deployment option', 'self-hosted vs cloud', or 'need lowest latency deployment'. Also use when choosing between deployment types for a new project.