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.
git 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/plugins/alexzio00/sovereign-skills/skill-ops)<a href="https://agentmods.dev/plugins/alexzio00/sovereign-skills/skill-ops"><img src="https://agentmods.dev/badge/plugins/alexzio00/sovereign-skills/skill-ops.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
skill-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 today.
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
{
"name": "skill-ops",
"description": "Skill ops hub: snapshot/rollback, usage health, and invocation tracking for Claude Code skills and agents.",
"version": "1.1.0",
"author": {
"name": "AlexZio00",
"url": "https://github.com/AlexZio00"
},
"homepage": "https://github.com/AlexZio00/sovereign-skills",
"repository": "https://github.com/AlexZio00/sovereign-skills",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 18 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- today Changed · +1 lines c7938cafb474
- 8d ago First seen · 12 lines scan A 7952447d0325
skill-ops is a plugin published in the GitHub repository AlexZio00/sovereign-skills (127 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
shipshitdev-dev-workflow
Code review, debugging, refactoring, release, and AI-assisted development workflows.
seqwalk
Walk through AI-written code with interactive HTML sequence diagrams.
flagrare
Development lifecycle skills: planning, quality gates, review, documentation, and design verification.
code-review
Correctness, security, and spec-fidelity gate for incoming pull requests. Auto-invoked when reviewing a diff, evaluating a PR, running /code-review at any effort level, or asked "is this safe to merge?" Covers bugs, TypeScript hygiene, security, database safety, test existence, devex regressions, feature-flag leaks…
merge-open-prs
Review and land open pull requests through one /merge command. The default mode runs a confirmation-gated trunk sweep and reports cleanup candidates; exact /merge force drains the queue non-serially by merging green PRs and narrowly fixing red PRs. Use when asked to review and merge open PRs, batch-merge to trunk…
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.