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.5 | $0.00026 | $0.00152 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (17 stars, last pushed 9d ago), licensed MIT. It adds 66 tokens to every session and 381 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-08-30.
Other skills, from other repositories
starcat-update-changelog
Update Starcat changelog documents in supports/starcat-pro/ by reading ALL git commits from the main Starcat project and generating categorized release notes in both English and Chinese. Use this skill whenever the user wants to update changelog, release notes, update records, or sync the changelog with recent…
starcat-release-readiness
A release-readiness workflow for preparing and auditing a macOS app for the Mac App Store and direct distribution. It covers checks across branches, database changes, tests, builds, signing, notarisation, release notes, and human approval.
release-notes
Compare the repository with the team's Folio wiki and write release notes: read git log since the last tag, read the Roadmap table, create or update a Release notes page and add what the roadmap table is missing. Use when asked for release notes or to sync the wiki with the code.
hyalo-changelog
Maintain Keep a Changelog files with Hyalo's changelog profile and add/release commands.
solomd
Read, search, edit, and version-control any folder of Markdown notes via the SoloMD MCP server. 13 tools including AutoGit per-note history, semantic search, and write-with-sandbox via an accept/reject branch. Includes 11 starter agent recipes (weekly review, todo extract, link suggester, …).
siyuan-plugin-development
Official frontend plugin development workflow. After the user explicitly opts in, clarify missing requirements, confirm a short plan, implement in a managed copy, verify, and package. Installation and activation require separate authorization.