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 rtorcato/repo-tooling --skill npm-publishgit clone --depth 1 https://github.com/rtorcato/repo-toolingWrote 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/rtorcato/repo-tooling/npm-publish)<a href="https://agentmods.dev/skills/rtorcato/repo-tooling/npm-publish"><img src="https://agentmods.dev/badge/skills/rtorcato/repo-tooling/npm-publish/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/rtorcato/repo-tooling/npm-publish"><img src="https://agentmods.dev/badge/skills/rtorcato/repo-tooling/npm-publish.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.00129 | $0.01080 |
| Opus 5 | $0.00064 | $0.00540 |
| Sonnet 5 | $0.00026 | $0.00216 |
| Haiku 4.5 | $0.00013 | $0.00108 |
Grade A, and why
npm-publish 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
npm-publish
A repo set up by @rtorcato/repo-tooling releases through automation on merge to
main — one of semantic-release, Changesets, or Release Please. Versioning, the
git tag, the GitHub release, the CHANGELOG, and the npm publish all come from that
pipeline. There is no manual release step under any of them.
The rule
Never run any of these — they fight the automation and corrupt the version line:
npm publish/pnpm publishnpm version(or editing"version"inpackage.json)git tag/ pushing tags- hand-editing
CHANGELOG.md - merging the "Version Packages" PR (Changesets) or the release PR (Release Please) — that merge is the publish, so it is the human's release decision, not yours
This holds for all three tools. Only the "what to do instead" differs, so first work out which tool the repo uses.
Which release tool is this repo on?
Check the repo root, in this order — these are the same signals the CLI's
doctor check uses (usesChangesets / checkSemanticRelease in
src/languages/js/checks.ts):
| Signal | Tool |
|---|---|
.changeset/config.json exists |
Changesets |
release-please-config.json exists |
Release Please |
.releaserc* / release.config.* exists, or a "release" key in package.json |
semantic-release |
Or just ask the tooling: npx @rtorcato/repo-tooling doctor --json reports the
semantic-release check as ok with a detail naming the tool actually in use.
If more than one is configured that's drift, not a choice — stop and flag it.
What to do instead, per tool
semantic-release
The bump is derived from the commit history, so the commit type is the release decision:
fix:→ patchfeat:→ minorfeat!:/BREAKING CHANGE:→ majorchore:/docs:/refactor:/test:→ no release
To ship a change: give it the right commit type and merge to main.
Changesets
The bump is declared in a changeset file, not inferred from commits. A PR with no changeset publishes nothing, silently — so this is a required step, not an optional one:
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 · 96 lines · 129 tokens per session scan A 4199e90a6589
npm-publish is a skill published in the GitHub repository rtorcato/repo-tooling (2 stars, last pushed 9d ago), licensed MIT. It adds 129 tokens to every session and 1,080 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.