Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add vinnie357/claude-skills/plugin install agent-sandboxingWrote 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/commands/vinnie357/claude-skills/status)<a href="https://agentmods.dev/commands/vinnie357/claude-skills/status"><img src="https://agentmods.dev/badge/commands/vinnie357/claude-skills/status.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.00027 | $0.00435 |
| Opus 5 | $0.00014 | $0.00217 |
| Sonnet 5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
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 3d 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
Show the live state of all SandboxClaims for at-a-glance triage.
Skills to load
/agent-sandboxing:k8s-agent-sandbox/core:nushell/core:anti-fabrication
Steps
1. Render the table
nu <CLAUDE_PLUGIN_ROOT>/scripts/list-claims.nu ${NAMESPACE:+--namespace $NAMESPACE}
The script wraps kubectl get sandboxclaim -o json, extracts session id, phase, template ref, bound pod, age, and shutdown policy, and emits a nushell table.
2. Annotate stuck claims
For any claim in Pending for >60 seconds, run:
kubectl describe sandboxclaim <name>
Common stuck-in-Pending causes:
- Missing RuntimeClass — controller condition will say
RuntimeClass "kata-qemu" not found. - ImagePullBackOff on the underlying pod —
kubectl get pod -l agent-sandbox.x-k8s.io/claim=<name>thendescribe pod. - Missing secret — controller condition will mention the referenced Secret.
- WarmPool drained —
kubectl describe sandboxwarmpoolshows 0 ready replicas.
Surface the actual condition text, not a guess.
3. Watch mode
If --watch was passed:
watch -n 2 "nu <CLAUDE_PLUGIN_ROOT>/scripts/list-claims.nu"
Or with kubectl directly:
kubectl get sandboxclaim -w
Anti-fabrication
- Don't summarize claim state from memory. Always re-run
kubectl getfor fresh data. - Don't claim a stuck claim is "almost ready" without timestamps to back it up — pull
metadata.creationTimestampand compare to now.
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.
- 3d ago First seen · 59 lines · 27 tokens per session scan A c0d8cd094b58
status is a command published in the GitHub repository vinnie357/claude-skills (24 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 435 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-09-03.
Other commands, from other repositories
runtime-logs
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
ci-fix
Fix CI pipeline issues with interactive approval.
debug-pod
Debug a failing or unhealthy Kubernetes pod by analyzing events, logs, and configuration.
debug
Structured platform troubleshooting — classifies the problem layer, collects evidence, forms a root-cause hypothesis, and proposes a fix with validation and rollback steps.
k8s-debug
Kubernetes debugging commands - troubleshoot pods, services, and cluster issues.
debug
Comprehensive debugging for Golden Armada agent services.