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/kubernetes-sigs/agent-sandbox/dev-rulesnpx skills add kubernetes-sigs/agent-sandbox --skill dev-rulesgit clone --depth 1 https://github.com/kubernetes-sigs/agent-sandboxWrote 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/kubernetes-sigs/agent-sandbox/dev-rules)<a href="https://agentmods.dev/skills/kubernetes-sigs/agent-sandbox/dev-rules"><img src="https://agentmods.dev/badge/skills/kubernetes-sigs/agent-sandbox/dev-rules.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.00013 | $0.00386 |
| Opus 5 | $0.00006 | $0.00193 |
| Sonnet 5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
dev-rules 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 4d 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
Development Rules
Purpose
This skill ensures that AI agents contributing to this project follow project-specific rules regarding code review and style to maintain compliance and quality.
Instructions
- Go Development: Follow standard Kubernetes Go patterns and best practices.
- AI-Assisted Code Reviews:
- Do NOT directly apply code suggestions from Copilot via the GitHub UI. Doing so adds Copilot as a co-author to the commit. Since Copilot cannot sign the Kubernetes CLA, this will cause the CLA check to fail and block the PR. Manual review and application of suggestions are required.
- Once the initial AI review (e.g., by Copilot) is complete, ensure all review comments are addressed and resolved so the PR can be labeled
ready-for-reviewfor maintainers.
- API Conventions: Always use the
k8s-api-conventionsskill when modifying APIs. - Creating Pull Requests: When creating a Pull Request, always use and fill out the project's PR template (
.github/pull_request_template.md).- Description: Provide a clear and concise description in the "What this PR does" section.
- Related Issues: Link related issues using "Fixes #issue" or "Ref link".
- Release Notes: Fill out the
release-noteblock. Note that automated release notes are generated from the description in the first section, so ensure it is comprehensive. For breaking changes, describe required actions and ask the maintainers to label the PR withrelease-note-action-required.
References
- Project rules (as documented in
CONTRIBUTING.md)
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.
- 4d ago First seen · 24 lines · 13 tokens per session scan A 6eb5197bee2d
dev-rules is a skill published in the GitHub repository kubernetes-sigs/agent-sandbox (3,733 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 386 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-30.
Other skills, from other repositories
troubleshoot-sandbox
Troubleshoot OpenSandbox issues by running diagnostics (logs, inspect, events, summary) via CLI or HTTP API to diagnose sandbox failures like OOM, crash, image pull errors, network problems, etc.
browse
Use the browse CLI for Browserbase browser automation, Browserbase cloud APIs, Browserbase Functions, templates, web fetch/search, diagnostics, and Browse.sh skill discovery/installation. Use when the user asks to navigate pages, inspect browser state, run local or remote browser sessions, manage Browserbase…
sanity-check
Run the deferred AgentOS E2E smoke test from public npm packages. Use when the user asks to sanity check, smoke test, or verify a release works.
launch-graphics
Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.
release
Cut an AgentOS release via the scripts/publish flow. Use when the user asks to release, publish, cut a release, or bump the AgentOS version.
release-preview
Cut an AgentOS release-preview. Use when the user asks for a preview, release-preview, or a branch dist-tag build.