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 louisbrulenaudet/monorepo-template --skill changesetgit clone --depth 1 https://github.com/louisbrulenaudet/monorepo-templateWrote 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/louisbrulenaudet/monorepo-template/changeset)<a href="https://agentmods.dev/skills/louisbrulenaudet/monorepo-template/changeset"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/changeset/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/louisbrulenaudet/monorepo-template/changeset"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/changeset.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.00087 | $0.00591 |
| Opus 5.5 | $0.00035 | $0.00236 |
| Sonnet 5.5 | $0.00017 | $0.00118 |
| Haiku 4.5 | $0.00009 | $0.00059 |
Grade A, and why
changeset 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 18d 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
Changeset
Writing, bump, and frontmatter rules live in rule ops/changesets (.claude/rules/ops/changesets.md; Cursor: .cursor/rules/ops/changesets.mdc). Read it first if it is not already loaded; this skill is only the procedure.
-
Scope. Read the branch diff (
git diff origin/main...HEAD --stat, plus uncommitted work) and split it into the changes a user or operator of a deployed app would notice. Note which apps each one reaches, including through a bundled@repo/*package or a runtime catalog bump. -
Reuse.
git diff --name-only --diff-filter=AM origin/main -- .changeset/lists this branch's changesets. If one already covers a change, edit it instead of adding another. If the change fixes something still pending onmain, edit that pending changeset. -
Decide per change, with the rule's tables:
- nothing observable ships:
--empty, or no changeset at all ifpnpm release:checkpasses without one; - otherwise
patchorminor, naming every app whose behavior changes and never an@repo/*package; - never
majorunless the user asked for a breaking release. While the apps are0.x, a breaking change isminorwith a**Breaking:**title.
- nothing observable ships:
-
Create one file per change, keeping the generated name:
pnpm changeset --patch worker-api,front-app -m "$(cat <<'EOF' Imperative title of at most 100 characters naming the surface in `backticks` Optional body: operator action, changed defaults, migration. EOF )"Use
--minorin the same form, orpnpm changeset --empty -m '<one-line reason>'. -
Verify.
git add .changeset/<id>.md, thenpnpm release:check. Fix everychangesets(<rule>)line it prints and rerun until it exits 0.pnpm release:statusshows the resulting versions. -
Report the file, the apps, and the bump in your reply and the PR description, and say why an
--emptyships nothing.
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.
- 18d ago First seen · 30 lines · 87 tokens per session scan A 323322c44325
changeset is a skill published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed today), licensed Apache-2.0. It adds 87 tokens to every session and 591 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-10-01.
Other skills, from other repositories
changelog
Update CHANGELOG.md with user-facing changes. Use when the user wants to update the changelog, prepare for a release, or document what changed since the last version.
changelog
Changelog Generation Command 📝.
release-rollback
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref. Behind an approval gate; with no previous good version it BLOCKS instead of…
release-tag
Cut a release tag behind a real tier gate and cloud approval readback. The approval, task, approved commit, and resulting tag are bound; self-approval and HEAD drift fail closed. Prod prefixes remain refused.
omh-deploy-and-monitor
This is an OMH deploy-and-monitor workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
github-release-briefing-skill
Create a source-linked briefing for the latest published GitHub release of a public repository. Use for engineering teams tracking a dependency release; do not use it to publish releases or change repositories.