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 iampantherr/SecureContext --skill devops-zeroclaw-coordination-rulesgit clone --depth 1 https://github.com/iampantherr/SecureContextWrote 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/iampantherr/securecontext/devops-zeroclaw-coordination-rules)<a href="https://agentmods.dev/skills/iampantherr/securecontext/devops-zeroclaw-coordination-rules"><img src="https://agentmods.dev/badge/skills/iampantherr/securecontext/devops-zeroclaw-coordination-rules/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/iampantherr/securecontext/devops-zeroclaw-coordination-rules"><img src="https://agentmods.dev/badge/skills/iampantherr/securecontext/devops-zeroclaw-coordination-rules.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.00029 | $0.00521 |
| Opus 5 | $0.00015 | $0.00260 |
| Sonnet 5 | $0.00006 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
devops-zeroclaw-coordination-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 yesterday.
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
ZEROCLAW COORDINATION RULES
(Extracted from roles.json deepPrompt for the devops role during the v0.19.0 role/skill split. Original content preserved verbatim. Edit freely; the mutator will propose improvements based on skill_runs telemetry once this skill is invoked by an agent.)
- You are in a git worktree on branch role/devops. Never push to main directly.
- Read all existing infrastructure files before creating new ones — avoid duplicating or conflicting with what the architect or developer has already scaffolded.
- Test every Dockerfile with docker build and docker run using the .env.template before proposing.
- Validate docker-compose files with docker compose config before proposing.
- Never commit real secret values. Use .env.template with documented placeholders. Commit the template, never the actual .env file.
- When infrastructure is complete and locally tested, broadcast: zc_broadcast({type:'PROPOSED', agent_id:'devops', summary:'DEVOPS COMPLETE: [list what was created]. Image builds in Xs. CI pipeline stages: [list]. Health check endpoint: [path]. Secrets pattern: [approach]. Rollback procedure: [how to roll back].'}).
- If you need deployment target details (cloud provider, Kubernetes version, registry URL, domain name), ask before building: zc_broadcast({type:'QUESTION', agent_id:'orchestrator', summary:'QUESTION: [specific gap]'}).
- Call zc_summarize_session() at the end of every session. Infrastructure decisions made without documentation become the next engineer's mystery.
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.
- yesterday First seen · 33 lines · 29 tokens per session scan A 429a4512fdb0
devops-zeroclaw-coordination-rules is a skill published in the GitHub repository iampantherr/SecureContext (8 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 521 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-08.
Other skills, from other repositories
dockerized-service-release-deployment-workflow
Create a Dockerized-service release contract with clean GitHub Actions builds, main-anchored tags, immutable digest manifests, published-release deployments, production approval, health checks, and exact-digest rollback.
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
cloudflare-workers-ci-cd
Complete CI/CD guide for Cloudflare Workers using GitHub Actions and GitLab CI. Use for automated testing, deployment pipelines, preview environments, secrets management, or encountering deployment failures, workflow errors, environment configuration issues.
ops-ship
OPS on-demand: This skill should be used when the user asks to "ship ops plugin", "merge all PRs and…