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 evergreen-it-dev/folio --skill release-notesgit clone --depth 1 https://github.com/evergreen-it-dev/folioWrote 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/evergreen-it-dev/folio/release-notes)<a href="https://agentmods.dev/skills/evergreen-it-dev/folio/release-notes"><img src="https://agentmods.dev/badge/skills/evergreen-it-dev/folio/release-notes/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/evergreen-it-dev/folio/release-notes"><img src="https://agentmods.dev/badge/skills/evergreen-it-dev/folio/release-notes.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.00063 | $0.00341 |
| Opus 5.5 | $0.00025 | $0.00136 |
| Sonnet 5.5 | $0.00013 | $0.00068 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
release-notes 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 6d 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 notes from the code and the wiki
Use the folio-wiki skill for how to work with Folio. This skill is the recipe.
- Find the last tag:
git describe --tags --abbrev=0. Readgit log <tag>..HEAD --oneline. If there are no tags, ask which commit to start from. - In Folio, find the release process page (
search_pages) and read it. Report which checklist items are still open. - Find the roadmap table (
folio_table_list), read its schema, then query the rows whose status is Done or In review. - Compare. Commits with no matching roadmap row are what the table is missing. Do not add rows on your own. List them and ask, unless the user already said to add them.
- Create a page called "Release notes" where the user said (usually under Engineering), or update the existing one. Keep it short: what shipped, grouped by area, each item linked to its roadmap row or page where one exists.
- Re-read the page, then answer with the link, the open checklist items and the commits that have no roadmap row.
Do not paste commit hashes of private branches or secrets from the diff into the wiki.
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.
- 6d ago First seen · 19 lines · 63 tokens per session scan A 8a143d61b3a9
release-notes is a skill published in the GitHub repository evergreen-it-dev/folio (69 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 341 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-10-09.
Other skills, from other repositories
ship-item
Ship a plan/todo item in a documentation-led repo — run the verify gate, integrate per the repo's model (fast-forward or PR), git mv todo→done with a shipped footer, advance the owning ADR(s) to Implemented, and regenerate INDEX. Use when the user says "ship this", "complete the plan item", "mark done", or "close out…
hyalo-changelog
Maintain Keep a Changelog files with Hyalo's changelog profile and add/release commands.
github-ops
Fast GitHub operations via the gh CLI. Use when the user mentions GitHub issues, PRs, repos, actions, releases, creating or triaging issues, opening or reviewing pull requests, managing branches, inspecting repo state, or checking CI. Works on any repo the operator's gh CLI is authenticated against.
changelog
Generate, update, review, and maintain changelogs using Keep a Changelog format, semantic-release, and conventional commits. Use this skill whenever the user wants to add a changelog entry, prepare release notes, document version changes, generate a changelog from git history, configure semantic-release, understand…
github-format-standards
Use when the user wants to share a project to GitHub. Runs a full pipeline: root audit, file naming and structure, document fixes (headings, code-block language tags, table alignment, explicit command interpreters), generate missing files (LICENSE, .gitignore, CONTRIBUTING.md, Issue/PR templates), README rewrite…
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.