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.
git clone --depth 1 https://github.com/Evyasys-Software-Solutions/EvyaGovernanceWrote 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/commands/evyasys-software-solutions/evyagovernance/generatereleasenote)<a href="https://agentmods.dev/commands/evyasys-software-solutions/evyagovernance/generatereleasenote"><img src="https://agentmods.dev/badge/commands/evyasys-software-solutions/evyagovernance/generatereleasenote/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/commands/evyasys-software-solutions/evyagovernance/generatereleasenote"><img src="https://agentmods.dev/badge/commands/evyasys-software-solutions/evyagovernance/generatereleasenote.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.00068 | $0.01052 |
| Opus 5 | $0.00034 | $0.00526 |
| Sonnet 5 | $0.00014 | $0.00210 |
| Haiku 4.5 | $0.00007 | $0.00105 |
Grade B, and why
GenerateReleaseNote scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
macOS / Linux (Bash): `EVYA_AI=$(find "$HOME/.claude/plugins" -maxdepth 6 -type d -name ".ai" 2>/dev/null | grep -i "EvyaGovernance" | head -1); [ -z "$EVYA_AI" ] && EVYA_AI=".ai"; echo "$EVYA_AI"` How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running /evyasys:GenerateReleaseNote.
Quick summary
-
Parse story IDs from
$ARGUMENTS. If none provided, ask: "Which story IDs should I include in this release? (e.g. EVYA-1042 EVYA-1043)" -
Find the plugin's installed workflow directory, then read the workflow files from it:
macOS / Linux (Bash):
EVYA_AI=$(find "$HOME/.claude/plugins" -maxdepth 6 -type d -name ".ai" 2>/dev/null | grep -i "EvyaGovernance" | head -1); [ -z "$EVYA_AI" ] && EVYA_AI=".ai"; echo "$EVYA_AI"Windows (PowerShell):
$EVYA_AI = (Get-ChildItem "$env:USERPROFILE\.claude\plugins" -Recurse -Directory -Filter ".ai" -ErrorAction SilentlyContinue | Where-Object { $_.FullName -like '*EvyaGovernance*' } | Select-Object -First 1 -ExpandProperty FullName); if (-not $EVYA_AI) { $EVYA_AI = ".ai" }; Write-Output $EVYA_AILoad from
<plugin-ai>/workflows/generate-release-note/(replace<plugin-ai>with the printed path). If any file is not found at the plugin path, fall back to the same filename under.ai/workflows/generate-release-note/:<plugin-ai>/workflows/generate-release-note/AGENT.md<plugin-ai>/workflows/generate-release-note/PROMPT.md<plugin-ai>/workflows/generate-release-note/CHECKLIST.md<plugin-ai>/workflows/generate-release-note/RELEASE_DOC_TEMPLATE.md.evyasys/workflows/generate-release-note/*.md(project overrides if any).evyasys/project.yaml(brand color, company name, output dir, naming convention).evyasys/memory/release-notes.json(version history)
-
For each story ID, locate
.evyasys/board/**/<id>/and read:<id>_UserStory.md— title, epic, story points, impacted areas<id>_ReleaseNotes.md— what's new, changelog, rollback (required — flag if missing)<id>_TestPlan.md— TC outcomes and quality gate results
-
Propose a version/release name from history + project naming convention. Confirm with user.
-
Draft the release document using
RELEASE_DOC_TEMPLATE.md:- Executive summary (3–5 sentences, no jargon)
- Stories grouped by Epic, each with user-facing changelog
- Consolidated quality gate table
- Known issues, deployment notes, rollback
-
Self-review with
CHECKLIST.md. Fix silently if any item fails. -
Show the complete document to the user. Tell them what files will be saved. Wait for approval.
-
On approval, output the
<!-- EVYARELEASE {...} -->block. -
The hook:
- Saves
.evyasys/releases/<name>_<date>.md(markdown) - Generates
.evyasys/releases/<name>_<date>.pdf(branded PDF via pdfkit) - Updates
.evyasys/memory/release-notes.json(release history) - Sends notification if configured
- Saves
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 · 70 lines · 68 tokens per session scan B ab110475a7c8
GenerateReleaseNote is a command published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 29d ago), licensed MIT. It adds 68 tokens to every session and 1,052 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
release-adr-kit
You are running the adr-kit release for version $ARGUMENTS (if empty, ask which version to release).
changelog
Generate a changelog from commits.
moodle-bump-version
You will bump the Moodle plugin version and wire the upgrade step.
wrap
Session-terminus driver — one /wrap runs the whole closing ceremony in order (coordinate teardown → checkpoint if warranted → recap → close-out → changelog → BACKLOG-shipped-row sweep → build-progress memory), driving the existing organs rather than reimplementing them. Auto-runs the reversible spine; every canonical…
close-out
Close out the scope chain on a shipped slug — reconcile shipped reality into the canonical spec, retire spent plan/blueprint artefacts to a dated archive folder, record one ship line. The terminus after /execute meets done-criteria.