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 cluster-simgit 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/cluster-sim)<a href="https://agentmods.dev/skills/paruff/ufawkesai/cluster-sim"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/cluster-sim.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.00032 | $0.00451 |
| Opus 5 | $0.00016 | $0.00226 |
| Sonnet 5 | $0.00006 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
cluster-sim 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.
What it actually says
Skill: Local Cluster Simulation
Load trigger:
"load cluster-sim skill"> DORA: Cap 3 (AI-Accessible Internal Data) Token cost: Low
Purpose
Run a local Kubernetes cluster for development and testing.
Responsibilities
- Start kind/k3d cluster
- Apply manifests
- Validate rollout
- Validate logs and metrics
Inputs
- Manifests
- Local cluster config
Outputs
cluster-sim.json
Cluster Options
| Tool | Use When |
|---|---|
| kind | Full K8s simulation, CI testing |
| k3d | Lightweight, fast startup |
| minikube | Single-node development |
Setup Commands
kind
kind create cluster --name dev --wait 60s
kind export kubeconfig --name dev
k3d
k3d cluster create dev --agents 2
Validation Rules
- Cluster starts successfully
- All nodes Ready
- System pods Running
- Manifests apply cleanly
- Pods reach Running state
Output Format
{
"skill": "cluster-sim",
"tool": "kind",
"cluster_name": "dev",
"status": "running",
"nodes": 1,
"system_pods": {
"total": 12,
"running": 12
},
"manifests_applied": 5,
"pods_running": 3
}
Success Criteria
- Local cluster behaves like production
- Fast startup (< 60 seconds)
- Manifests apply cleanly
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 · 90 lines · 32 tokens per session scan A a200685ee4a0
cluster-sim is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 16d ago), licensed MIT. It adds 32 tokens to every session and 451 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…
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.
harness
To build an AI harness: run, observe, validate, automate repeated work faster — CLI/MCP actions, devcontainers, skills, subagents, hooks, pipelines, automations.
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.