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 agentmods add commands/evyasys-software-solutions/evyagovernance/setupgit 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/setup)<a href="https://agentmods.dev/commands/evyasys-software-solutions/evyagovernance/setup"><img src="https://agentmods.dev/badge/commands/evyasys-software-solutions/evyagovernance/setup.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 | $0.00057 | $0.00497 |
| Opus 5 | $0.00028 | $0.00249 |
| Sonnet 5 | $0.00011 | $0.00099 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade B, and why
Setup 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 4d 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:Setup.
Step 0 — Load the workflow ⛔ HARD GATE
First — find the plugin's installed workflow directory (do this before any file read):
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
Use the printed path in place of .ai for every workflow file read below. If a file is not found at the plugin path (older install), fall back to the same path under .ai/. Then read both files:
<plugin-ai>/workflows/setup/AGENT.md— your agent role and rules<plugin-ai>/workflows/setup/PROMPT.md— the full step-by-step wizard
Do not ask any questions, do not read project files, and do not take any action until you have loaded both files.
Once you have read both files, follow the PROMPT.md wizard exactly — one question at a time — and at the end output the <!-- EVYACONFIG { ... } --> block exactly as the PROMPT.md instructs.
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.
- 4d ago First seen · 32 lines · 57 tokens per session scan B bab7020975d3
Setup is a command published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 23d ago), licensed MIT. It adds 57 tokens to every session and 497 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
create-new-package-in-monorepo
Create a new buildable TypeScript package in the Packmind monorepo using Nx tools and configure it for use across applications.
CLAUDE
The "commands" domain — multi-step coding commands, their versions, and their deployment.
story-implement
Implement a story through the Implement Phase. Stories must be fully designed with chunks before implementation.
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
sprint
Scope-boxed sprints over the backlog: one active sprint, explicit carry-over, a close that refuses to hide unfinished work.
story-new
Create a new story. It lands in the backlog until assigned to a cycle.