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/pre-push)<a href="https://agentmods.dev/plugins/alexzio00/sovereign-skills/pre-push"><img src="https://agentmods.dev/badge/plugins/alexzio00/sovereign-skills/pre-push.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
pre-push 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 8d 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
{
"name": "pre-push",
"version": "6.0.0",
"description": "Mandatory pre-push pipeline — secrets scan (12 patterns), build/test gate, lint, parallel AI code review. Blocks push on Critical/High findings.",
"author": {
"name": "AlexZio00",
"url": "https://github.com/AlexZio00"
},
"homepage": "https://github.com/AlexZio00/sovereign-skills",
"repository": "https://github.com/AlexZio00/sovereign-skills",
"license": "MIT",
"keywords": [
"pre-push",
"secrets-scan",
"code-review",
"security",
"lint",
"ci",
"pipeline"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 144 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.
- 8d ago First seen · 22 lines scan A 592ebcfa1403
pre-push 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
github-dev
Git and GitHub workflow skills for commits, PRs, code review, and comment resolution.
technical-deslop
Clean branch/staged diffs by removing AI-style slop and restoring repo-consistent style without changing behavior.
deep-implement
Implement code from /deep-plan sections with TDD, code review, and git workflow.
sequant
AI coding agent orchestrator for Claude Code — resolve GitHub issues end-to-end with isolated git worktrees and quality gates, through spec → exec → qa phases.
loop
Turn any repo into a supervised multi-agent loop: spawn parallel coding agents in git worktrees, track them on a radar, and keep a human in the approval loop.
finishing-a-development-branch
Structured "done coding, now what?" workflow: verify tests pass, detect the repository environment (normal repo vs worktree, named branch vs detached HEAD), present exactly the right merge / PR / keep / discard options, and execute the chosen path including safe worktree cleanup. Use when implementation is complete…