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 aka-kika/kika-obsidian-mcp --skill release-note-captaingit clone --depth 1 https://github.com/aka-kika/kika-obsidian-mcpWrote 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/aka-kika/kika-obsidian-mcp/release-note-captain)<a href="https://agentmods.dev/skills/aka-kika/kika-obsidian-mcp/release-note-captain"><img src="https://agentmods.dev/badge/skills/aka-kika/kika-obsidian-mcp/release-note-captain/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/aka-kika/kika-obsidian-mcp/release-note-captain"><img src="https://agentmods.dev/badge/skills/aka-kika/kika-obsidian-mcp/release-note-captain.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.00066 | $0.00381 |
| Opus 5 | $0.00033 | $0.00191 |
| Sonnet 5 | $0.00013 | $0.00076 |
| Haiku 4.5 | $0.00007 | $0.00038 |
Grade A, and why
release-note-captain 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 11d 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
Release Note Captain
Create or update an Obsidian release note when a project is deployed, published, or finished.
Destination
Default folder:
Release Notes/
Default filename:
YYYY-MM-DD — Project Name.md
Use vault-relative paths only. If the release note already exists, read it first and update it instead of creating a duplicate.
Required Fields
Include these sections unless the user asks for a different format:
- Project
- Date
- Status
- Repo URL
- Live URL, if available
- Summary
- What Shipped
- Verification
- SEO/GEO or Distribution Notes
- Follow-Ups
Workflow
- Gather release facts from the conversation, repo, deploy output, GitHub, or local files.
- Use
list_notesorget_noteto check whether a release note already exists. - Create the folder
Release Notesif missing. - Create or update the release note.
- Keep wording useful for both public release history and private project memory.
- End with the note path and any missing details that still need the user.
Style
- Clear and compact.
- Prefer bullets for shipped changes and verification.
- Include exact URLs and commit hashes when available.
- Avoid hype. State what shipped and why it matters.
- Preserve unfinished follow-ups instead of burying them.
Template
Use templates/release-note.md as the base structure when creating a new note.
What ships with it
1 file 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.
- 11d ago First seen · 62 lines · 66 tokens per session scan A 50c6ded7d31d
release-note-captain is a skill published in the GitHub repository aka-kika/kika-obsidian-mcp (14 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 381 once invoked, about $0.0003 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-30.
Other skills, from other repositories
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). Verify, commit. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
utility-pm-release-conductor
Walk the guided 6-gate release runbook (G0 readiness, G1 adversarial review, G2 version bump and CHANGELOG, G2.5 commit and re-verify, G3 tag and push, G4 post-tag hygiene) via the pm-release-conductor sub-agent. Refuses gate bypasses and tags only the re-verified SHA. Use when cutting a pm-skills release.
deliver-release-notes
Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language. Use when shipping updates to communicate changes to users, customers, or stakeholders.
utility-pm-changelog-curator
Draft CHANGELOG entries from git log via the pm-changelog-curator sub-agent, applying the repo hygiene rules (describe what changed, public paths only, no attribution trailers). Returns a layered draft with a status summary for maintainer review; refuses a dirty working tree unless --committed-only is passed. Use when…