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-statusgit 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-status)<a href="https://agentmods.dev/skills/rhtevan/agentfs/crc-status"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/crc-status/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-status"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/crc-status.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.00012 | $0.00755 |
| Opus 5.5 | $0.00005 | $0.00302 |
| Sonnet 5.5 | $0.00002 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
crc-status 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 26d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenShift Local Status & Banner Cleanup
Read-only health check for an OpenShift Local (CRC) cluster. Reports cluster state, resource usage, and optionally removes the default caution banner from the OpenShift web console. This skill never starts, stops, or modifies the CRC cluster itself — it only observes and reports.
Prerequisites
crcCLI installedocCLI installed (for banner check/removal)
Scope & Boundaries
⚠️ This is a status-check skill. Do NOT start, stop, restart, or reconfigure CRC. If the cluster is stopped, report that fact and stop. The user will decide whether to start it.
| In scope | Out of scope |
|---|---|
| Report CRC VM and OpenShift state | Starting or stopping CRC |
| Report disk and cache usage | Changing CRC configuration |
| Check for and remove the console banner | Troubleshooting CRC failures |
| Report credentials | Installing or updating CRC |
Steps
Step 1 — Check CRC status
Run crc status to read the current cluster state.
crc status
Step 2 — Evaluate state (decision point)
| CRC VM State | Agent Action |
|---|---|
| Running | Proceed to Step 3 |
| Stopped | Report status to user. STOP here. Do NOT proceed. |
| Starting / Stopping | Report transitional state to user. STOP here. |
| Error / other | Report the full output to user. STOP here. |
⛔ Hard gate: Steps 3–6 require a running cluster. If CRC is not in
Runningstate, the skill ends at Step 2. Do NOT attempt to start CRC or work around the stopped state.
Step 3 — Get console credentials
Run crc console --credentials to retrieve the kubeadmin login
command.
crc console --credentials
Step 4 — Log in as admin
Log in to the cluster using the credentials from Step 3:
oc login -u kubeadmin -p <password> https://api.crc.testing:6443
Step 5 — Check for the caution banner
Look for the default ConsoleNotification resource:
What ships with it
1 file 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.
- 26d ago Changed · +59 lines 159665c84c1d
- 1mo ago First seen · 53 lines · 12 tokens per session scan A 39c098a368aa
crc-status is a skill published in the GitHub repository rhtevan/agentfs (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 12 tokens to every session and 755 once invoked, about $0.0000 per session on Opus 5.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
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".