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/bouob/sysadmin-skills/done-opsnpx skills add bouob/sysadmin-skills --skill done-opsgit clone --depth 1 https://github.com/bouob/sysadmin-skillsWrote 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/bouob/sysadmin-skills/done-ops)<a href="https://agentmods.dev/skills/bouob/sysadmin-skills/done-ops"><img src="https://agentmods.dev/badge/skills/bouob/sysadmin-skills/done-ops.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.00070 | $0.00780 |
| Opus 5 | $0.00035 | $0.00390 |
| Sonnet 5 | $0.00014 | $0.00156 |
| Haiku 4.5 | $0.00007 | $0.00078 |
Grade A, and why
done-ops 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operations Verification Gate
Core principle: Evidence before claims, always.
The Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If the service has not been verified as operational in this session, the task cannot be claimed as complete.
Related Skills
- /incident — loads this skill before closing an incident
- /change-request — loads this skill before finalizing a change
- itil — provides the process framework for closure criteria
This skill is loaded as a gate by /incident and /change-request. It does not need to be invoked directly when using those workflows.
The Gate
Before claiming any operational task is complete:
- IDENTIFY — what evidence proves resolution/completion?
- VERIFY — confirm the evidence is current (not from memory or earlier checks)
- DOCUMENT — record the verification in the output document
- CONFIRM — does the evidence satisfy the closure criteria?
- NO → state actual status with evidence, identify remaining actions
- YES → state claim WITH evidence
Verification Requirements by Task Type
Incident Closure
| Check | Required Evidence |
|---|---|
| Service restored | Service is accessible and functioning (confirmed by monitoring or manual test) |
| User confirmation | Affected user/team confirms the issue is resolved |
| Monitoring stable | No recurring alerts for the affected component within the observation period |
| Documentation complete | Timeline, actions taken, resolution, and follow-up items recorded |
| Problem record | Created if root cause is unknown or incident is recurring |
| Communication sent | Resolution notification sent to all parties who received the initial alert |
| SLO compliance checked | (Optional) Error budget impact estimated; note if budget is now < 10% |
Change Request Closure
| Check | Required Evidence |
|---|---|
| Implementation complete | All steps in the implementation plan executed |
| Validation passed | Post-implementation checks confirm expected behavior |
| No regression | Related services unaffected (checked, not assumed) |
| Rollback not triggered | No rollback criteria were met during implementation |
| PIR scheduled | Post-Implementation Review scheduled within required timeframe |
| Users notified | Affected users informed of completion (if applicable) |
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 · 93 lines · 70 tokens per session scan A 8ea42601754c
done-ops is a skill published in the GitHub repository bouob/sysadmin-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 780 once invoked, about $0.0003 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
servicenow-change-management
ITSM change-management operations on the ServiceNow Change API via the servicenow-api MCP server — the full change-request lifecycle: query changes, tasks, schedules, CIs, models and standard-change templates; create/update changes and change-tasks; run risk calculation and conflict checks; approve; and delete. Use…
binary-analysis
Analyze binary files (exe, dll, sys, bin, ocx, scr, cpl, drv, elf, so, macho, apk) to assess if they are malicious, perform decompilation, extract strings/imports/exports, detect malware, and provide threat assessment. Use this skill when user asks to analyze, examine, check, or assess any binary file, asks if a file…
kernel-cve-analysis
Query the Android/AOSP kernel CVE database to look up a specific CVE, find CVEs affecting a kernel version or build date, find unpatched CVEs in a branch, or identify exploitable vulnerabilities. Use this skill when the user asks about Android kernel CVEs, AOSP kernel vulnerabilities, which CVEs affect a kernel…
spill-scrub
Find and scrub credentials that leaked into Claude Code's own local logs (transcripts, paste-cache, shell snapshots, /.claude.json). Use when the user mentions a spillage, a leaked or pasted secret, "clean the logs", "scrub my transcripts", "I pasted a key", "did a token get logged", or after any incident where a…
pace-biz
Use when user says "业务机会/OPP", "专题/Epic", "分解需求/decompose", "精炼/refine", "战略对齐/align", "业务全景/view", "需求发现/brainstorm/discover", "导入/import", "技术债务/infer", "pace-biz", or wants to plan requirements. NOT for /pace-dev, -change, -plan, -init.
pace-change
Use when user says "不做了", "搁置", "停掉", "加一个", "加需求", "追加", "改需求", "需求变了", "范围变了", "优先级调", "延后", "提前", "砍掉", "先做这个", "排到前面", "恢复", "捡回来", "pace-change", or wants to add, pause, resume, reprioritize, modify, undo, batch change, or query change history. NOT for code implementation (/pace-dev) or project init (/pace-init).