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/finishqa)<a href="https://agentmods.dev/commands/evyasys-software-solutions/evyagovernance/finishqa"><img src="https://agentmods.dev/badge/commands/evyasys-software-solutions/evyagovernance/finishqa/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/finishqa"><img src="https://agentmods.dev/badge/commands/evyasys-software-solutions/evyagovernance/finishqa.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.00031 | $0.00684 |
| Opus 5 | $0.00015 | $0.00342 |
| Sonnet 5 | $0.00006 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade B, and why
FinishQa 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 9d 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"` What it actually says
You are running /evyasys:FinishQa $ARGUMENTS.
If $ARGUMENTS is empty, ask for the StoryID.
-
Find the plugin's installed workflow directory, then load all files under
<plugin-ai>/workflows/finish-qa/(+ project overrides). If any file is not found at the plugin path, fall back to the same filename under.ai/workflows/finish-qa/.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_AI -
Find the story folder by globbing
.evyasys/board/**/<StoryID>/. Read<StoryID>_UserStory.md(for Impacted Areas flags) and<StoryID>_TestPlan.md. If any TC has no recorded outcome (pass/fail/blocked), stop and ask the user to fill it in first. Do not proceed until all TCs have outcomes. -
Verify no P0/P1 defects remain open against this story. If yes: list them. Gate cannot proceed until resolved or formally accepted.
-
Verify AC sign-off: every AC has a passing test case or is formally waived by the Product Owner.
-
Run domain-specific gates based on Impacted Areas flags: Security (SECURITY.md), Performance (PERFORMANCE.md), Accessibility (DESIGN_SYSTEM.md), Data Integrity (DB_STANDARDS.md). Mark each ✅ / ❌ / N/A.
-
Check architect gate: if QA surfaced any doc gaps in SECURITY.md or PERFORMANCE.md, flag those docs for update.
-
Draft release notes using
RELEASE_NOTES_TEMPLATE.md: one plain-language paragraph (no jargon, no class names), bullet changelog, known limitations, roll-back plan. -
Self-review against
CHECKLIST.md. Show to user and wait for approval. -
On approval → save
<StoryID>_ReleaseNotes.mdto story folder → ADO Done → Teams release card.
Output: release notes path · ADO state.
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.
- 9d ago First seen · 27 lines · 31 tokens per session scan B 82fac82392bc
FinishQa is a command published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 27d ago), licensed MIT. It adds 31 tokens to every session and 684 once invoked, about $0.0002 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
speckit.spex.finish
Smoke test + squash + merge/keep (land the code on main).
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.
4-close-project
Name: 4-close-project Purpose: Apply an OpenSpec change through TDD, verify it, prepare or update the PR, and leave archive for after merge.
explore-release
This legacy command is a rename notice only. Its workflow is now rpi-explore-release.
moodle-bump-version
You will bump the Moodle plugin version and wire the upgrade step.