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 BlackBeltTechnology/pi-agent-dashboard --skill release-revokegit clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboardWrote 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/blackbelttechnology/pi-agent-dashboard/release-revoke)<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/release-revoke"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/release-revoke/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/blackbelttechnology/pi-agent-dashboard/release-revoke"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/release-revoke.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 157 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.
- medium Excessive Agency · line 154 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.00085 | $0.01651 |
| Opus 5 | $0.00043 | $0.00826 |
| Sonnet 5 | $0.00017 | $0.00330 |
| Haiku 4.5 | $0.00009 | $0.00165 |
Grade A, and why
release-revoke 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Revoke a pi-agent-dashboard Release
This skill undoes a release cut by the release-cut skill. It handles
three layers independently because they have different semantics:
| Layer | Revocable? | Mechanism |
|---|---|---|
| GitHub Release | Yes (draft or published) | gh release delete |
| Git tag | Yes | git push --delete + git tag -d |
| Electron artifacts | Yes (deleted with release) | handled by gh release delete |
| npm package | Effectively permanent | npm deprecate (NOT unpublish) |
Key fact about npm: npm unpublish is blocked 72h after publish, or
any time the version has dependents. The right "revoke" for an npm
release is npm deprecate, which leaves the tarball in place but marks
it with a warning visible to anyone who tries to install it.
Step 1 — Select version
Run:
git tag -l 'v*' | sort -V | tail -10
Use AskUserQuestion (select) showing the last 10 tags. Do NOT auto-pick.
Store the chosen version as <version> (with the leading v).
Step 2 — Inspect current state
gh release view <version> --json isDraft,publishedAt,assets,url 2>/dev/null || echo "NO_RELEASE"
git tag -l <version> # local tag exists?
git ls-remote --tags origin <version> # remote tag exists?
npm view @blackbelt-technology/pi-dashboard@${version#v} version 2>/dev/null || echo "NOT_ON_NPM"
Parse results and report to the user:
- Whether GitHub Release exists (draft vs published)
- Whether the tag exists locally / on origin
- Whether this version is on npm
Step 3 — Confirm intent
Use AskUserQuestion (confirm) with a full impact preview, e.g.:
About to revoke <version>:
• GitHub Release: PUBLISHED — will be deleted (artifacts gone)
• Git tag: exists locally + on origin — will be deleted from both
• npm: published <N> days ago — will be deprecated
(npm unpublish not possible: > 72h old / has dependents)
This is PARTIALLY REVERSIBLE:
• GitHub Release + tag can be re-created by re-tagging.
• npm deprecation CAN be reversed with `npm deprecate <pkg>@<v> ""`.
• npm version number is burned — cannot republish same version.
Proceed?
What ships with it
1 file 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.
- 11d ago First seen · 177 lines · 85 tokens per session scan A 96b5d7cdb53b
release-revoke is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (278 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 1,651 once invoked, about $0.0004 per session on Opus 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-30.
Other skills, from other repositories
akiship
Full release ritual end-to-end — front-loaded checks, then an unattended pass. ACTIVATION IS LITERAL: this skill runs only on a user turn containing the exact token /akiship that asks for the run to be performed. Nothing else activates it — not the bare word "akiship", not a release-flavored paraphrase, and never a…
public-plugin-packaging
Use when packaging an Agentlas agent repo for public GitHub release, Codex plugin submission, Claude adapter distribution, or one-line terminal installation.
akigitcommit
Analyze the working tree and commit changes in clean logical groups. Triages a long half-finished tree first (finished vs mid-edit vs abandoned vs accidental) before grouping. Auto-detects CHANGELOG to switch between domain-grouped mode (3–5 commits by object/feature) and type-grouped mode (feat/fix/refactor). Stages…
starfleet-github
GitHub PR/CI/backport interaction via starfleetctl (read-only + mutating commands, PR claims, backports). Load when checking PR status/CI, claiming a PR branch, submitting or repairing a PR, or backporting.
starfleet-sessions
Ship session and workspace management — spawning ships, session attach/stop, git worktrees, web console, deployment. Load when launching/administering ships or managing the fleet web console.
agency-jira-workflow-steward
Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.