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 pau-vega/Devkit-AI --skill release-please-monorepogit clone --depth 1 https://github.com/pau-vega/Devkit-AIWrote 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/pau-vega/devkit-ai/release-please-monorepo)<a href="https://agentmods.dev/skills/pau-vega/devkit-ai/release-please-monorepo"><img src="https://agentmods.dev/badge/skills/pau-vega/devkit-ai/release-please-monorepo/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/pau-vega/devkit-ai/release-please-monorepo"><img src="https://agentmods.dev/badge/skills/pau-vega/devkit-ai/release-please-monorepo.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.00127 | $0.01811 |
| Opus 5 | $0.00063 | $0.00905 |
| Sonnet 5 | $0.00025 | $0.00362 |
| Haiku 4.5 | $0.00013 | $0.00181 |
Grade A, and why
release-please-monorepo 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 10d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Please for pnpm/Turbo Monorepos
Automated, Conventional-Commits-driven releases: one Release Please PR accumulates version bumps + changelogs per package; merging it tags a release and triggers per-package publish jobs. Each package versions independently.
Prerequisites (must exist first)
- Conventional Commits enforced. Release Please reads commit types (
feat,fix, …) to decide bump level. Enforce via commitlint + Huskycommit-msghook. Allowed types map to changelog sections in the release-please config. Seereferences/templates.md→ "commitlint config". - One
package.jsonper publishable package withname,version(synced with manifest),publishConfig.registry,repository.directory,files,private: false. Seereferences/templates.md→ "package shape". - Registry auth wiring. For GitHub Packages: root
.npmrcsets@scope:registry=https://npm.pkg.github.com; CI usesNODE_AUTH_TOKEN+setup-noderegistry-url+scope. Seereferences/templates.md→ ".npmrc".
Skip any of the above and releases will mis-bump, fail to publish, or publish to the wrong registry.
Files to create
Four files live in .github/. Full contents in references/templates.md:
| File | Purpose | Hand-edited? |
|---|---|---|
.github/release-please-config.json |
Per-package config: release-type, package-name, component, changelog-sections. | Yes, when adding a package. |
.github/.release-please-manifest.json |
Source of truth for each package's current version. | No — Release Please updates it on release. Seed once per package. |
.github/workflows/release-please.yml |
The workflow: one release-please job + N publish jobs + optional post-release job. | Yes, when adding a package's publish job. |
Workflow anatomy
Single workflow, one release-please job + one publish job per package. Pattern from references/templates.md → "workflow":
release-please (runs on every push to main)
→ outputs: release_created, releases_created, tag_name, version, paths_released
publish-<pkg> (needs: release-please, if: contains(paths_released, '<pkg-path>'))
→ checkout (fetch-depth: 1) → pnpm setup → setup-node (registry-url, scope, cache: pnpm)
→ cache .turbo → pnpm install --frozen-lockfile --filter=<pkg>...
→ pnpm turbo build --filter=<pkg>
→ pnpm config set registry auth (or rely on setup-node env)
→ cd packages/<pkg> && pnpm publish --no-git-checks
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.
- 10d ago First seen · 84 lines · 127 tokens per session scan A 72108457a08e
release-please-monorepo is a skill published in the GitHub repository pau-vega/Devkit-AI (2 stars, last pushed 25d ago), licensed MIT. It adds 127 tokens to every session and 1,811 once invoked, about $0.0006 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-31.
Other skills, from other repositories
last-tag
Show commits since the last tag in a formatted table. Use when user asks "what changed since last release", "commits since last tag", "last-tag", "what's new", or wants to see recent unreleased changes.
ship
Ship a build — pre-flight checks, deploy, document, verify, monitor. Use when deploying code, publishing packages, or releasing.
release
Prepare a version release — bump version files, commit, and tag. Just run /release with no arguments.
release-init
Detect project type and generate a tailored project-level /release skill. Run once per project to set up releasing.
release-plugin
Cut a cairn plugin release for a given MAJOR.MINOR.PATCH version, running every pre-flight and version gate before anything is changed or published.
release-app
Cut a workhub release — bump the app version, write the changelog entry, commit to main, tag vX.Y.Z, push, and verify the GitHub Release published with every required asset. Use when the user wants to release or ship the workhub app, tag a version, or publish a build.