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 keithhegit/ultra-orchestration --skill ultra-risk-vettinggit clone --depth 1 https://github.com/keithhegit/ultra-orchestrationWrote 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/keithhegit/ultra-orchestration/ultra-risk-vetting)<a href="https://agentmods.dev/skills/keithhegit/ultra-orchestration/ultra-risk-vetting"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/ultra-risk-vetting/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/keithhegit/ultra-orchestration/ultra-risk-vetting"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/ultra-risk-vetting.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.00059 | $0.00414 |
| Opus 5.5 | $0.00024 | $0.00166 |
| Sonnet 5.5 | $0.00012 | $0.00083 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
ultra-risk-vetting 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 2mo 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
Ultra Risk Vetting
Classify risk before execution. This skill is the vNext replacement for the
stable risk-vetter skill and absorbs the approval-facing part of
safety-guard.
Risk Levels
Use four levels:
LOWsafe, local, reversible, narrow-scope workMEDIUMnormal engineering work with bounded writes or commandsHIGHbroad writes, destructive operations, publishing, credentials, or external systemsEXTREMEirreversible, secret-exposing, production-impacting, legal, financial, or security-sensitive actions
Gate Rules
LOW: proceed and log brieflyMEDIUM: proceed with guardrails and evidence captureHIGH: stop for explicit user approval unless the user already gave concrete approval for the exact actionEXTREME: block by default and ask for explicit approval plus scope confirmation
Vetting Checklist
Before execution, inspect:
- reversibility
- write scope
- command destructiveness
- external network or system effects
- credential or secret exposure
- production or user data impact
- whether the action changes published state
- whether the action can be safely retried
Output
Return a VetterDecision:
risk_leveldecisionrequired_guardrailsapproval_requiredevidence_to_capturereasoning_summaryresidual_risk
Record the decision in vetter_report and hand required guardrails to
ultra-execution-control.
Read risk-policy for examples and thresholds.
What ships with it
2 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.
- 2mo ago First seen · 65 lines · 59 tokens per session scan A 5bbeceed5817
ultra-risk-vetting is a skill published in the GitHub repository keithhegit/ultra-orchestration (6 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 414 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-08-31.
Other skills, from other repositories
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.
dependency-upgrade
Plan, batch, and verify dependency upgrades safely. Triages outdated packages into risk tiers, upgrades in order (dev/minor/patch first, runtime majors last), verifies each batch, and produces an auditable commit sequence. Use when asked to "upgrade deps", "bump packages", "update nodemodules", "fix vulnerabilities"…
forensics
Post-mortem a failed GSD auto-mode run. Traces symptom to root cause via .gsd/ activity, journal, metrics, and lock artifacts, producing a filing-ready bug report with file:line refs and a fix suggestion. Use when asked to "forensics", "post-mortem", "why did auto-mode fail", "trace the stuck loop", "debug the crash"…
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…