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 JimmyPaolini/codebase --skill publish-releasegit clone --depth 1 https://github.com/JimmyPaolini/codebaseWrote 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/jimmypaolini/codebase/publish-release)<a href="https://agentmods.dev/skills/jimmypaolini/codebase/publish-release"><img src="https://agentmods.dev/badge/skills/jimmypaolini/codebase/publish-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/jimmypaolini/codebase/publish-release"><img src="https://agentmods.dev/badge/skills/jimmypaolini/codebase/publish-release.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.00048 | $0.00466 |
| Opus 5.5 | $0.00019 | $0.00186 |
| Sonnet 5.5 | $0.00010 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
publish-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 26d 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
Publish and Release
Build Output and Publishing
- Every build writes into its own project's
dist/—packages/logger/dist,applications/caelundas/dist— never a top-level one.distis already gitignored and in the folder-structure rule'signorePatterns. configuration/tsconfig.jsonsetsdeclaration: true, so every build emits.d.tsbeside its.js. Turning it off silently removes the types a published package ships.- A package's
main,types, andexportspoint at TypeScript sources, andpublishConfigcarries the emitteddist/paths beside them — pnpm applies those at publish time, so one manifest serves the workspace and a published consumer. Verify a change here by packing, not by reading:pnpm packin the package, then inspect the tarball'spackage.json. filesmust namedist. Without it, packing falls back to the ignore files and the tarball ships no build output at all.- A plugin entry's
resolvePluginServicemust stay a static import. A dynamicimport()escapes the@swc-node/registerrequire hook into Node's own ESM resolver, andnx gthen fails withCannot find module './modules/plugin/plugin-context.utilities'.
Why the manifest fields stay on sources, which publishConfig fields pnpm
actually applies, and why shrinking the Nx plugin closure buys nothing is
ADR 0009. Do
not point main or exports at dist/ — it deadlocks the plugin graph load
and breaks fallow-dead-code and vitest.
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.
- 26d ago First seen · 34 lines · 48 tokens per session scan A 9dfeb7a38bb9
publish-release is a skill published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed 19d ago), licensed MIT. It adds 48 tokens to every session and 466 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-09-20.
Other skills, from other repositories
release-process
Pre-release validation, npm publish procedures, and post-publish verification.
package-release-engineering
Use when preparing, validating, or documenting the release workflow for a TypeScript library published to npm, including semver, changelog, tagging, and publish safety.
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
create-draft-pr
Create a draft pull request for the current session. Use when the user wants to open a draft PR with the session's changes.
create-pr
Create a pull request for the current session. Use when the user wants to open a PR with the session's changes.