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/diagnose)<a href="https://agentmods.dev/commands/evyasys-software-solutions/evyagovernance/diagnose"><img src="https://agentmods.dev/badge/commands/evyasys-software-solutions/evyagovernance/diagnose/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/diagnose"><img src="https://agentmods.dev/badge/commands/evyasys-software-solutions/evyagovernance/diagnose.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.00081 | $0.00461 |
| Opus 5 | $0.00041 | $0.00230 |
| Sonnet 5 | $0.00016 | $0.00092 |
| Haiku 4.5 | $0.00008 | $0.00046 |
Grade B, and why
Diagnose 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.
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:Diagnose.
Step 0 — Load workflow
First — find the plugin's installed workflow directory:
macOS / Linux — run via 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 — run via 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
Then load these files from <plugin-ai>/workflows/diagnose/ (fall back to .ai/workflows/diagnose/ if not found at the plugin path):
AGENT.md— the diagnostician rolePROMPT.md— the 20 checksCHECKLIST.md— the self-review
Follow PROMPT.md exactly. Run every check in parallel where possible. Emit the human-readable report and the structured <!-- EVYADIAGNOSE ... --> tail.
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 · 30 lines · 81 tokens per session scan B 15e2130d917a
Diagnose is a command published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 27d ago), licensed MIT. It adds 81 tokens to every session and 461 once invoked, about $0.0004 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
recover
Reconcile pipeline-state.json against git reality for one, several, or all in-flight REQs and bugs. Diagnoses each as in-sync, stale-state, abandoned, sprint-stuck, or divergent, then surfaces a triage queue and back-fills the vault for REQs whose code shipped without /wrapup running. Read-only on code and git…
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
commit
Review staged changes and create a commit.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
vouch-resolve-issue
Use vouch's KB to ground a fix for a GitHub issue.