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 simota/agent-skills --skill guardiangit clone --depth 1 https://github.com/simota/agent-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/simota/agent-skills/guardian)<a href="https://agentmods.dev/skills/simota/agent-skills/guardian"><img src="https://agentmods.dev/badge/skills/simota/agent-skills/guardian/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/simota/agent-skills/guardian"><img src="https://agentmods.dev/badge/skills/simota/agent-skills/guardian.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 113 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00062 | $0.04103 |
| Opus 5.5 | $0.00025 | $0.01641 |
| Sonnet 5.5 | $0.00012 | $0.00821 |
| Haiku 4.5 | $0.00006 | $0.00410 |
Grade A, and why
guardian 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- guardian — 97% identical, 102 lines differ
How it starts
The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What ships with it
21 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.
- _common 10 B
- reference/autorun-mode.md 1.8 KB
- reference/branch-health.md 2.4 KB
- reference/branching-strategies.md 3.0 KB
- reference/collaboration-routing.md 7.6 KB
- reference/commit-analysis.md 2.9 KB
- reference/coverage-integration.md 1.8 KB
- reference/git-recipes.md 8.7 KB
- reference/history-audit.md 6.7 KB
- reference/history-reshape.md 8.5 KB
- reference/learning-loop.md 2.9 KB
- reference/output-templates.md 5.6 KB
- reference/pr-quality-scoring.md 3.3 KB
- reference/pr-ship-flow.md 11 KB
- reference/pr-split-strategy.md 13 KB
- reference/pr-workflow-patterns.md 6.4 KB
- reference/predictive-quality-gate.md 1.9 KB
- reference/recipes-index.md 1.8 KB
- reference/risk-assessment.md 4.2 KB
- reference/security-analysis.md 3.3 KB
- reference/squash-optimization.md 2.3 KB
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 Changed · +1 lines 0d85feb51835
- 5d ago Changed 1a1da3a919c7
- 6d ago Changed · +30 tokens per session ed98d7bfee59
- 11d ago Changed 9fd5b8092c25
- 1mo ago Changed 897c9155e4c0
- 1mo ago Changed · -1 lines f123cae5e995
- 1mo ago Changed · -30 lines 973f4d4c8235
- 1mo ago First seen · 311 lines · 32 tokens per session scan A 0cf99788e0cb
guardian is a skill published in the GitHub repository simota/agent-skills (94 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 4,103 once invoked, about $0.0002 per session on Opus 5.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-03.
Other skills, from other repositories
pr-authoring
Playbook for deployment-aware pull requests — the 11-section format that turns a PR into a reviewable contract; why, decision requested, change map, review order, evidence, verification, risk, rollback. Used for the Define→build handoff and any PR a great-pm-driven project opens.
pr-review
Playbook for reviewing pull requests — verdict format, verification-not-trust, severity-ranked findings with concrete fixes, risk acceptance on the record. The reviewer-side counterpart of pr-authoring.
feature-publish
Commit the feature, write the PR body, publish in the selected mode, and drive the PR.
lean-review
CocoLean diff-scoped over-engineering audit — scans uncommitted git diff and applies five classification tags (delete/stdlib/native/yagni/shrink) to identify unnecessary surface area before commit.
commit-and-push
Create a well-formatted git commit and push to remote repository.
effect-ledger
Record an effect, sign an effect, reconcile an effect or check "did this PR merge" through the signed AIWG effect ledger, using one aiwg effect command with scriptable exit codes.