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 agentmods add commands/arc-mcp/arc-1/release-notesgit clone --depth 1 https://github.com/arc-mcp/arc-1What 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 | $0.00000 | $0.00864 |
| Opus 5 | $0.00000 | $0.00432 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
release-notes 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 2d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes — annotate a release for the docs
Turn a raw release-please changelog entry into an annotated release entry in
docs_page/release-notes.md — the page users and LLMs read to
understand what a release actually changed for them.
CHANGELOG.md is machine-generated and stays that way: one line per merged PR, no context. This
command adds the context next to it, never inside it.
When to run
While the release-please PR is open, before merging it. The PR body already contains the exact
changelog entry for the upcoming version, so the notes can land first and main never goes red.
Also run it whenever a released version is missing from the page — tests/unit/server/release-notes.test.ts
fails with the list.
Input
A version (1.0.1), a release-please PR number, or nothing (then annotate every version present in
CHANGELOG.md but missing from docs_page/release-notes.md).
Method
- Get the raw entry — from the open release-please PR body (
gh pr view <n> --json body) or fromCHANGELOG.mdfor an already-released version. - Read what actually changed — for each line:
git show <sha> --stat, then the diff of the parts that matter. The PR title is a hint, not evidence.gh pr view <n>for the description where useful. - Find the user-visible surface — for each change, answer concretely:
- New or changed env var / CLI flag? (
src/server/types.ts,docs_page/configuration-reference.md) - New or changed tool, action, object type, or parameter? (
src/handlers/tools.ts, and thetests/fixtures/tool-definitions/*.jsondiff — that file is the LLM-visible surface) - Behavior change an existing setup would notice? Breaking? Security-relevant?
- Which
docs_page/*.mdpage documents it now?
- New or changed env var / CLI flag? (
- Write the entry using the template below, newest-first, above the previous version.
- Verify —
npx vitest run tests/unit/server/release-notes.test.ts, and check every relative doc link resolves to a file that exists. The guard counts a version as annotated only when it has its own##/###heading or is the first cell of a table row — a mention in prose does not satisfy it.
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.
- 2d ago First seen · 75 lines · 0 tokens per session scan A 604b0850ab15
release-notes is a command published in the GitHub repository arc-mcp/arc-1 (174 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 864 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.