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/ericlovold/sanction/render-checknpx skills add ericlovold/sanction --skill render-checkgit clone --depth 1 https://github.com/ericlovold/sanctionWhat 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.00088 | $0.00950 |
| Opus 5 | $0.00044 | $0.00475 |
| Sonnet 5 | $0.00018 | $0.00190 |
| Haiku 4.5 | $0.00009 | $0.00095 |
Grade D, and why
render-check scanned grade D with 3 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo -u postgres /usr/lib/postgresql/16/bin/pg_ctl status -D /var/lib/postgresql/16/main Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- `rm -rf .next` — stale dev artifacts have broken `tsc` on later gates Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. **Assert fast, then look**: `curl | grep` for the load-bearing strings The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 71 lines · 88 tokens per session scan D d6184f72c44c
render-check is a skill published in the GitHub repository ericlovold/sanction (2 stars, last pushed 2d ago), with no licence file. It adds 88 tokens to every session and 950 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
drift-review
Analyze behavioral drift patterns across agents. Use when reviewing agent health, investigating anomalies, or during periodic governance reviews.
hold-triage
Review and process pending governance holds. Use when holds are waiting for human approval or when the user asks about blocked operations.
governance-setup
Configure PromptSpeak governance for a new project. Use when first setting up PromptSpeak or when the user wants to customize governance policies.
graphify
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community…
xcodebuildmcp-structured-output-review
Use when reviewing XcodeBuildMCP structured output schema changes, schema versioning, manifest outputSchema metadata, and JSON fixture compatibility.
repro
Turn a bug symptom into a structured, reproducible bug report — summary, environment, exact repro steps, actual vs expected, and evidence (logs, error text, failing route/test) — and then optionally scaffold a failing regression test that pins it. Use this the moment a bug, defect, crash, 500, wrong count, broken…