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 agentmods add skills/xobotyi/cc-foundry/provisioningnpx skills add xobotyi/cc-foundry --skill provisioninggit clone --depth 1 https://github.com/xobotyi/cc-foundryWrote 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/xobotyi/cc-foundry/provisioning)<a href="https://agentmods.dev/skills/xobotyi/cc-foundry/provisioning"><img src="https://agentmods.dev/badge/skills/xobotyi/cc-foundry/provisioning.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 | $0.00102 | $0.03471 |
| Opus 5 | $0.00051 | $0.01736 |
| Sonnet 5 | $0.00020 | $0.00694 |
| Haiku 4.5 | $0.00010 | $0.00347 |
Grade A, and why
provisioning 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 5d 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grafana Provisioning
Make Grafana resources reproducible. Pick the right tool for each resource type and team workflow, then keep the runtime configuration in sync with version control. Wrong tool choices don't cause errors immediately — they show up months later as drift, brittle CI, or notification policies overwritten by a partial config push.
References
- File provisioning — [
${CLAUDE_SKILL_DIR}/references/file-provisioning.md] Directory layout, env var interpolation, full datasource / dashboard / plugin / alerting YAML schemas, reload behavior, UI edit semantics - HTTP API — [
${CLAUDE_SKILL_DIR}/references/http-api.md] New/apis/Kubernetes-style surface vs. legacy/api/, dashboard / folder / datasource CRUD, alerting provisioning endpoints, annotation API, pagination, authentication - Terraform — [
${CLAUDE_SKILL_DIR}/references/terraform.md] Provider setup, full resource catalog, dashboards / datasources / alerting examples, provenance and UI-edit toggle, GitHub Actions workflow, import workflow - gcx — [
${CLAUDE_SKILL_DIR}/references/gcx.md] Grafana CLI install, contexts, resource pull/push/serve, telemetry queries, agentic features and skills, CI integration, migration fromgrafanactl - Observability as code — [
${CLAUDE_SKILL_DIR}/references/observability-as-code.md] Tool comparison, decision matrix, how to compose tools, migration paths (Grizzly → gcx, legacy API → new API, file → Terraform)
Tool selection
Pick the primary tool based on resource type and team workflow. The references above contain a full decision matrix — quick selection rules:
- Self-managed Grafana, simple setup → file provisioning
- Dev → staging → prod resource migration →
gcx(Grafana ≥ v12) - Dashboards generated programmatically → Foundation SDK +
gcx - Agentic coding tools driving Grafana from the terminal →
gcx - Git as source of truth, edits via Grafana UI → Git Sync
- Already running Terraform → Grafana Terraform provider
- Kubernetes-native GitOps shop → Grafana Operator or Crossplane
- One-off scripts and custom integrations → HTTP API directly
- Grafana Cloud only with existing Ansible → Grafana Ansible Collection
- Existing grafanactl deployment, Grafana < v12 → continue with
grafanactluntil upgrading; the binary keeps working through the 2026-06-01 archive date
What ships with it
6 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.
- 5d ago First seen · 343 lines · 102 tokens per session scan A 312f921235f4
provisioning is a skill published in the GitHub repository xobotyi/cc-foundry (20 stars, last pushed 2d ago), licensed MIT. It adds 102 tokens to every session and 3,471 once invoked, about $0.0005 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…