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/startqa)<a href="https://agentmods.dev/commands/evyasys-software-solutions/evyagovernance/startqa"><img src="https://agentmods.dev/badge/commands/evyasys-software-solutions/evyagovernance/startqa.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.00039 | $0.00627 |
| Opus 5 | $0.00019 | $0.00313 |
| Sonnet 5 | $0.00008 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade B, and why
StartQa 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 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.
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:StartQa $ARGUMENTS.
If $ARGUMENTS is empty, ask for the StoryID.
-
Find the plugin's installed workflow directory, then load all files under
<plugin-ai>/workflows/start-qa/(+ project overrides). If any file is not found at the plugin path, fall back to the same filename under.ai/workflows/start-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,<StoryID>_DevSummary.md, and<StoryID>_CodeReview.md(if available) from that folder. Runpython scripts/repo_scan.py --story $ARGUMENTS --diff. -
Ask clarifying questions one at a time per
QUESTIONING.md(environment required, test data required if stateful, flaky areas, browser matrix for UI). Wait for each answer. Do not write test cases until environment and data are confirmed. -
Write test plan using
TEST_PLAN_TEMPLATE.md: for every AC write ≥ 1 positive + ≥ 1 negative case. Add edge cases, regression checks for every touched file, non-functional section (perf/security/a11y or N/A with reason). Use Gherkin for multi-step scenarios. -
Self-review against
CHECKLIST.md. Show to user and wait for approval. -
On approval → save
<StoryID>_TestPlan.mdto story folder → ADO In QA → Teams card.
Output: test plan 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.
- 6d ago First seen · 24 lines · 39 tokens per session scan B 568891535c79
StartQa is a command published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 25d ago), licensed MIT. It adds 39 tokens to every session and 627 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
tdd
Test-driven development with tests that actually catch breaks: red before green, name the break each test catches, and the mutation check before done.
ci
CI/CD hygiene and run health: pinned actions, timeouts, concurrency, tests — plus the latest runs via gh.
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.
api-contract
Manage API contracts — OpenAPI, gRPC, GraphQL, breaking-change detection.
test
Run tests, analyze failures, and propose fixes.
traceability-gen
Regenerate traceability.md from specs + plans + tests.