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 ijust/intent-planner --skill intent-release-notegit clone --depth 1 https://github.com/ijust/intent-plannerWrote 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/ijust/intent-planner/intent-release-note)<a href="https://agentmods.dev/skills/ijust/intent-planner/intent-release-note"><img src="https://agentmods.dev/badge/skills/ijust/intent-planner/intent-release-note/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/ijust/intent-planner/intent-release-note"><img src="https://agentmods.dev/badge/skills/ijust/intent-planner/intent-release-note.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.00042 | $0.02714 |
| Opus 5.5 | $0.00017 | $0.01086 |
| Sonnet 5.5 | $0.00008 | $0.00543 |
| Haiku 4.5 | $0.00004 | $0.00271 |
Grade A, and why
intent-release-note 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 2mo 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
intent-release-note Skill
Core Mission
- Success Criteria:
- Read the git log of the given range (default = latest tag..HEAD;
<from>..<to>may be given via argument, with fallback) read-only (no commit / tag creation / push). - Text-match each commit against intent (packet name / parent intent / deltas) and, for matched ones, attach the "why (for which intent it changed)."
- List unmatched commits as thin changelog lines, surfacing the gap between intent and reality (do not silently drop them).
- Derive output under
.intent/release-note/following a format (selectrules/format-changelog.md/rules/format-github-releases.md/rules/format-changelog-customer.md/rules/format-pr-description.md/rules/format-trajectory.mdby argument) by full replacement. - Change neither the canonical intent (intent-tree / compass / packets) nor the git state (INV16 / INV17).
- Read the git log of the given range (default = latest tag..HEAD;
Execution Steps
Step 1: Range interpretation (fix the range)
- When the user runs
/intent-release-note, first interpret the range argument perrules/source-scope.md. - The default (no range given) is latest tag..HEAD (find the latest tag with
git describe --tags --abbrev=0and use<tag>..HEAD). If<from>..<to>is given, use it. - If there is no latest tag and the default cannot be resolved, fall back to the full history and note this in the output (Fail-Soft). An invalid range argument is an explicit error and does not generate a release note.
- Once the range is fixed, proceed to Step 2 (the range is uniquely determined by argument + default + fallback, not dependent on interactive completion).
Step 2: Read-only reading of the git log
- Per the read-only allowlist in
rules/source-scope.md, read the commits of the fixed range read-only. - Only read-only
git log/git tag(listing) /git describe/git rev-list/git rev-parse/git showmay be used. - Never invoke writing operations (
git commit/git tag <name>creation /git push/git checkout/git switch/git reset/git restore/git merge/git rebase/git cherry-pick, etc.) (INV16). - Read each commit's hash, subject, body, author, and date as material.
What ships with it
7 files 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.
- 2mo ago First seen · 76 lines · 42 tokens per session scan A b6a889caa081
intent-release-note is a skill published in the GitHub repository ijust/intent-planner (5 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 2,714 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-08-31.
Other skills, from other repositories
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
git-workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…
contributing
Codex adapter for the opencode-swarm contribution checklist. Use when preparing user-visible changes, release note fragments, local validation, branch hygiene, PR checklist items, or contribution-policy compliance before publishing work.
finishing-a-development-branch
Use when implementation is complete, tests pass, and you need to decide the integration path. Also use when asked to prepare a branch for release: 'update changelog', 'bump version', 'bump patch version', 'make sure changelog is correct', 'make sure version is correct'. Triggers: 'done with this branch', 'ready to…
context-mode-ops
Manage context-mode GitHub issues, PRs, releases, and marketing with parallel subagent army. Orchestrates 10-20 dynamic agents per task. Use when triaging issues, reviewing PRs, releasing versions, writing LinkedIn posts, announcing releases, fixing bugs, merging contributions, validating ENV vars, testing adapters…
vc:publish
Push agent harness improvements from the current development repo to the remote kit repository. Use when you want to publish local harness changes back to the shared kit. Diffs managed files, shows what changed, bumps version, and pushes.