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 porcupine-md/jonggrang --skill documenting-releasegit clone --depth 1 https://github.com/porcupine-md/jonggrangWrote 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/porcupine-md/jonggrang/documenting-release)<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/documenting-release"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/documenting-release.svg" alt="Measured on agentmods" 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.00020 | $0.00451 |
| Opus 5 | $0.00010 | $0.00226 |
| Sonnet 5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
documenting-release 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 8d 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
Documenting Release
Role Constraints: Lead (Write/Bash access allowed).
File Access: Do NOT use literal placeholders for file paths. Use the glob tool to search for the active feature directory under .jonggrang/.output/features/.
Objective
Ensure every documentation file in the project is accurate, up to date, and written in a friendly, user-forward voice before the feature is fully released.
Execution Steps
- Pre-flight & Diff Analysis:
- Use
bashto rungit diff main...HEAD --stat(or the appropriate base branch) to understand what changed. - Classify changes into features, changed behavior, removals, and infrastructure.
- Use
- Per-File Documentation Audit:
- Locate major documentation files (
README.md,ARCHITECTURE.md,CHANGELOG.md,CONTRIBUTING.md) usingglob. - Read each file and cross-reference it against the git diff.
- Locate major documentation files (
- Apply Factual Updates:
- Use the
editorwritetool to make factual corrections directly (e.g., adding a command to a table, updating counts). - Use the
bashtool if you need to run specific scripts that generate documentation.
- Use the
- CHANGELOG Voice Polish:
- If
CHANGELOG.mdexists, review the entry for the current feature. - Polish the wording to focus on user capabilities ("You can now...") rather than implementation details. Do NOT delete or regenerate existing entries, only refine them.
- If
- Ask About Risky Changes:
- If narrative changes, security model descriptions, or massive rewrites are needed, ask the user for confirmation before proceeding.
- Cross-Doc Consistency Check:
- Ensure the
READMEaligns withARCHITECTUREandCHANGELOG. Fix any clear factual inconsistencies.
- Ensure the
Completion Signal
When the documentation has been updated and verified, output exactly:
DOCUMENTATION_COMPLETE
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.
- 8d ago First seen · 39 lines · 20 tokens per session scan A f9196f12e6ba
documenting-release is a skill published in the GitHub repository porcupine-md/jonggrang (11 stars, last pushed 12d ago), licensed MIT. It adds 20 tokens to every session and 451 once invoked, about $0.0001 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-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.