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 rhtevan/agentfs --skill crc-post-setup-configgit clone --depth 1 https://github.com/rhtevan/agentfsWrote 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/rhtevan/agentfs/crc-post-setup-config)<a href="https://agentmods.dev/skills/rhtevan/agentfs/crc-post-setup-config"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/crc-post-setup-config/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/rhtevan/agentfs/crc-post-setup-config"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/crc-post-setup-config.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.00017 | $0.01424 |
| Opus 5.5 | $0.00007 | $0.00570 |
| Sonnet 5.5 | $0.00003 | $0.00285 |
| Haiku 4.5 | $0.00002 | $0.00142 |
Grade A, and why
crc-post-setup-config scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Active silence visible via `oc exec -n openshift-monitoring alertmanager-main-0 -c alertmanager -- curl -s 'http://localhost:9093/api/v2/silences'` How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRC Post-Setup Configuration
Apply post-setup configuration to an OpenShift Local (CRC) cluster. This skill combines all one-time tuning that must be re-applied after every crc delete && crc start cycle.
What It Configures
| Area | What | Why |
|---|---|---|
| Cluster Monitoring | Enables the monitoring stack with aggressive Prometheus retention (24h / 4GB) |
CRC disables monitoring by default; without retention limits Prometheus fills the VM disk |
| System Reserved Resources | Overrides kubelet --system-reserved to memory=1Gi, cpu=500m, ephemeral-storage=1Gi via a MachineConfig |
CRC's default reservation (350Mi memory) is too low and triggers the SystemMemoryExceedsReservation alert |
| Alert Silences | Silences AlertmanagerReceiversNotConfigured for 1 year |
Expected on a dev cluster with no external notification receivers configured |
Steps
Part 1 — Enable Cluster Monitoring
-
Verify the cluster is reachable
oc whoami oc cluster-info -
Set the CRC config flag This persists across
crc delete+crc start, so a fresh cluster will also enable monitoring:crc config set enable-cluster-monitoring true -
Remove the monitoring overrides from ClusterVersion CRC disables monitoring by adding
unmanaged: trueoverrides to the ClusterVersion resource for thecluster-monitoring-operatorDeployment and themonitoringClusterOperator. Remove only these two entries while keeping all other overrides intact.- Fetch the current overrides:
oc get clusterversion version -o jsonpath='{.spec.overrides}' | python3 -m json.tool - Build a new overrides list that excludes the two monitoring entries:
{"kind":"Deployment","name":"cluster-monitoring-operator","namespace":"openshift-monitoring"}{"kind":"ClusterOperator","name":"monitoring"}
- Patch the ClusterVersion with the filtered list:
oc patch clusterversion version --type=json \ -p '[{"op":"replace","path":"/spec/overrides","value": <filtered list> }]' - If the overrides array is already free of monitoring entries, skip this step.
- Fetch the current overrides:
What ships with it
4 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.
- 1mo ago First seen · 125 lines · 17 tokens per session scan A 720d49f2f6d5
crc-post-setup-config is a skill published in the GitHub repository rhtevan/agentfs (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 1,424 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
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 generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
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…
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".