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 AlexZio00/sovereign-skills --skill skill-opsgit clone --depth 1 https://github.com/AlexZio00/sovereign-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/alexzio00/sovereign-skills/skill-ops)<a href="https://agentmods.dev/skills/alexzio00/sovereign-skills/skill-ops"><img src="https://agentmods.dev/badge/skills/alexzio00/sovereign-skills/skill-ops/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/alexzio00/sovereign-skills/skill-ops"><img src="https://agentmods.dev/badge/skills/alexzio00/sovereign-skills/skill-ops.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.03921 |
| Opus 5 | $0.00009 | $0.01961 |
| Sonnet 5 | $0.00004 | $0.00784 |
| Haiku 4.5 | $0.00002 | $0.00392 |
Grade C, and why
skill-ops scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
[ -n "${path}" ] && rm -rf -- "${path}" How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/skill-ops v1.2
Skill/agent ops hub — 3 modes: snapshot, usage, frequency. Merges skill-versioning + skill-health-report.
Dominant Variable
Snapshot integrity + invocation log completeness — if a snapshot doesn't match the original, rollback is meaningless. Without logs, usage analysis is impossible.
Key Assumptions
- Permission to create
~/.claude/.harness/snapshots/— if broken: report permission issue + provide manual mkdir command. - Target file is
~/.claude/skills/*/SKILL.mdor~/.claude/agents/*.md— if broken: ask for the skill name directly. - Retention policy: keep last 5 — 6th and older are deleted oldest-first. Ignore if deletion fails.
- Invocation logs: session-checkpoint Phase 3.7 appends to
invocations/YYYY-MM.jsonl— if broken: state "no logs". - SKILLS/AGENTS_INVENTORY.md is the source of truth — if broken: analyze from log-derived names only (mark incomplete).
Trigger
/skill-ops(snapshot default)/skill-ops health/skill-ops invocations- "skill version", "skill usage frequency", "harness score"
Discard If
- Target file is outside
~/.claude/skills/or~/.claude/agents/(project code → git handles it) - Target file doesn't exist (nothing to snapshot)
- A same-day snapshot with an identical SHA-256 content hash already exists (duplicate is pointless)
- Health mode:
invocations/directory itself doesn't exist → report "no logs" - Health mode: 0 JSONL files within scan range → report "no logs in range"
Mode
| Mode | Role | Trigger |
|---|---|---|
| snapshot | Pre-change snapshot + regression-detection restore command | /skill-ops (default) |
| health | Usage/Dead/Unused/Discard report | /skill-ops health |
| invocations | Per-skill frequency rollup from session JSONL | /skill-ops invocations |
Snapshot Mode
Phase 0: Parse Input
- Extract target file path from user input (absolute path > skill name > user question)
- Extract skill name:
~/.claude/skills/<name>/SKILL.mdor~/.claude/agents/<name>.md
What ships with it
4 files 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.
- 4d ago Changed · +10 lines aa85e81fe3af
- 11d ago First seen · 268 lines · 18 tokens per session scan C 4b15dc84def0
skill-ops is a skill published in the GitHub repository AlexZio00/sovereign-skills (128 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 3,921 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
nobrainer-review
Use when the owner says nb-review, deep-audit, deep-code-review, or deep-autoreview; explicitly requests an evidence-gated CLOSEOUT, adversarial BUGHUNT or RELEASEGATE; or needs final findings filtered to verified actionable defects. Use nobrainer-build for ordinary implementation and correction work.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
ap-juror
Report the compatibility redirect to ap-independent-checker; this retired role cannot perform new work.
ijfw-cross-audit
Generate a cross-platform multi-model audit (Trident) on a diff, brief, or artifact. Trigger: 'cross audit', 'Trident', 'second opinion', 'check with other models', 'check with other AIs', 'cross-check this', 'get another perspective', /cross-audit.
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now…