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-nmstate-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-nmstate-config)<a href="https://agentmods.dev/skills/rhtevan/agentfs/crc-nmstate-config"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/crc-nmstate-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-nmstate-config"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/crc-nmstate-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.00018 | $0.01246 |
| Opus 5 | $0.00009 | $0.00623 |
| Sonnet 5 | $0.00004 | $0.00249 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
crc-nmstate-config 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.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRC NMState Operator Configuration
Install the NMState Operator on OpenShift Local (CRC) and verify that the console plugin and networking menu items are working correctly.
Prerequisites
- CRC cluster is running (
crc statusshows Running) ocis logged in askubeadmin(oc whoamireturnskubeadmin)- OpenShift Console is accessible
Step 1: Create Namespace, OperatorGroup, and Subscription
Apply all three resources in one pass:
oc apply -f - <<EOF
apiVersion: v1
kind: Namespace
metadata:
name: openshift-nmstate
---
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
name: openshift-nmstate
namespace: openshift-nmstate
spec:
targetNamespaces:
- openshift-nmstate
---
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
name: kubernetes-nmstate-operator
namespace: openshift-nmstate
spec:
channel: stable
name: kubernetes-nmstate-operator
source: redhat-operators
sourceNamespace: openshift-marketplace
EOF
Step 2: Wait for the Operator to Be Ready
Wait for the CSV to reach Succeeded phase:
oc get csv -n openshift-nmstate --watch
Expected output eventually shows:
kubernetes-nmstate-operator.v... kubernetes-nmstate-operator ... Succeeded
Step 3: Create the NMState Instance
oc apply -f - <<EOF
apiVersion: nmstate.io/v1
kind: NMState
metadata:
name: nmstate
EOF
Step 4: Wait for All NMState Pods to Be Running
oc get pods -n openshift-nmstate --watch
Expected running pods:
nmstate-console-plugin-*nmstate-handler-*(DaemonSet, one per node)nmstate-metrics-*nmstate-operator-*nmstate-webhook-*
Step 5: Verify CRDs Are Present
oc get crd | grep nmstate
Expected output includes:
nodenetworkconfigurationenactments.nmstate.io
nodenetworkconfigurationpolicies.nmstate.io
nodenetworkstates.nmstate.io
Step 6: Verify Console Plugin Is Registered
The NMState operator automatically registers nmstate-console-plugin and adds it to the console. Verify:
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.
- 8d ago First seen · 172 lines · 18 tokens per session scan A a5dc72d80887
crc-nmstate-config is a skill published in the GitHub repository rhtevan/agentfs (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,246 once invoked, about $0.0001 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
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.