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 emanuelcasco/pi-mono-extensions --skill releasegit clone --depth 1 https://github.com/emanuelcasco/pi-mono-extensionsWrote 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/emanuelcasco/pi-mono-extensions/release)<a href="https://agentmods.dev/skills/emanuelcasco/pi-mono-extensions/release"><img src="https://agentmods.dev/badge/skills/emanuelcasco/pi-mono-extensions/release/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/emanuelcasco/pi-mono-extensions/release"><img src="https://agentmods.dev/badge/skills/emanuelcasco/pi-mono-extensions/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Tool Misuse · line 148 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00086 | $0.02402 |
| Opus 5.5 | $0.00034 | $0.00961 |
| Sonnet 5.5 | $0.00017 | $0.00480 |
| Haiku 4.5 | $0.00009 | $0.00240 |
Grade A, and why
release 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.
How it starts
The opening of the file, as written. The whole thing — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Skill — pi-extensions
Cut a new release for the pi-extensions monorepo. The repo uses changesets with independent versioning — each package under extensions/* versions independently based on its own unreleased changes. Releases are pushed directly to main — no PRs.
Repo facts (load-bearing)
- Versioning tool:
@changesets/cli(config in.changeset/config.json) - Versioning mode: independent —
fixedarray is empty; each package tracks its own version - Tag format: per-package tags like
[email protected](created by changesets publish) - GitHub repo:
emanuelcasco/pi-mono-extensions - Publish script:
pnpm release(runschangeset publish) - npm publish requires being logged in (
npm whoamishould return a username); if it fails with auth errors, stop and tell the user to runnpm login
Workflow
1. Gather context
Run in parallel:
git status -sb
git tag --sort=-v:refname | head -20
gh release list --limit 5
git log --oneline $(git tag --sort=-v:refname | head -1)..HEAD
ls extensions/
cat .changeset/config.json
For each extension, also collect its current version:
for d in extensions/*/; do echo "$(basename $d): $(cat $d/package.json | jq -r .version)"; done
From this, determine:
- Per-package current versions — read from each
extensions/*/package.json - Latest tag — first matching
pi-mono-*@X.Y.Z - Unreleased commits — what's landed since the last tag
- Which packages have changes — use
git log <last-tag>..HEAD --name-onlyto identify whichextensions/*/directories have unreleased commits - Per-package bump type — for each package with changes, infer from commit messages touching that package:
feat:→ minorfix:/chore:/refactor:→ patch- Breaking change (
!orBREAKING CHANGE) → major
- Working tree clean? — if not, ask the user before proceeding
Display a summary table:
| Package | Current | Bump | New | Unreleased |
|----------------------|---------|----------|----------|------------|
| pi-mono-team-mode | 1.6.0 | minor | 1.7.0 | 2 commits |
| pi-mono-clear | 0.3.1 | patch | 0.3.2 | 1 commit |
| pi-mono-loop | 0.2.0 | — | 0.2.0 | 0 commits |
| pi-mono-status-line | 0.1.4 | minor | 0.1.5 | 3 commits |
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 · 254 lines · 86 tokens per session scan A 5a5c24c2bf82
release is a skill published in the GitHub repository emanuelcasco/pi-mono-extensions (108 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 2,402 once invoked, about $0.0003 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-30.
Other skills, from other repositories
releasing-code
Prepare, publish, or repair a software release and write its release notes. Use for cutting a versioned release or editing release notes. NOT for updating an installed package, publishing articles, or discussing a release; for general documentation use documenting-code.
shipping
Project shipping is authorized immediate delivery execution for identified, already-completed software work. Select only when the user explicitly authorizes an immediate concrete action to commit, push, prepare or create a PR, merge, tag, package, publish, release, deploy, perform an exact repository handoff, or…
changelog
Use when updating the changelog for a release.
public-release
Use when auditing a repository before making it public.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.