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 skills/ijust/intent-planner/intent-release-notenpx skills add ijust/intent-planner --skill intent-release-notegit clone --depth 1 https://github.com/ijust/intent-plannerWhat 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.00042 | $0.02714 |
| Opus 5 | $0.00021 | $0.01357 |
| Sonnet 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 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 — 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.
- 2d 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 2d ago), licensed MIT. It adds 42 tokens to every session and 2,714 once invoked, about $0.0002 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
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
office-hours
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to…
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
echo
Use when the user references past sessions, asks 'what did we do', 'do you remember', 'last session', 'recall', or 'continue from'.