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/startdevgit 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/startdev)<a href="https://agentmods.dev/commands/evyasys-software-solutions/evyagovernance/startdev"><img src="https://agentmods.dev/badge/commands/evyasys-software-solutions/evyagovernance/startdev.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.00049 | $0.01119 |
| Opus 5 | $0.00024 | $0.00560 |
| Sonnet 5 | $0.00010 | $0.00224 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade B, and why
StartDev 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 5d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running /evyasys:StartDev $ARGUMENTS.
If $ARGUMENTS is empty, ask: "Which story or epic IDs should I start dev for? (e.g. EVYA-1042, EP-001, or EP-001 EVYA-1005)"
Step 0 — Pre-flight (before any analysis)
0a. Load CLAUDE.md, .ai/rules/*.md, .evyasys/rules/*.md (project overrides win).
These govern every approach you propose — no option may violate architecture layers or quality rules.
0b. Resolve all IDs from $ARGUMENTS:
- Epic ID (e.g. EP-001): glob .evyasys/board/epics/{epicId}/stories/*/ to find all story sub-folders and expand to their story IDs. Show: "Resolved N stories in {epicId}: EVYA-1001, EVYA-1002 …"
- Story ID (e.g. EVYA-1042): add as-is.
Deduplicate. Report the final list of story IDs before proceeding.
0c. For each resolved story ID, scan .evyasys/board/**/<id>/ for existing artefacts:
- Hard stop (per story): if <id>_UserStory.md is not found, skip this story and show: "Cannot start dev for <id> — no story file found. Run /evyasys:CreateStory first."
- If <id>_TechBrainstorm.md already exists, ask: "Resume existing brainstorm or start fresh?"
- If <id>_DevSummary.md exists, warn the user before continuing.
If every story in the batch fails the hard stop, abort. If only some fail, continue with the remaining valid stories.
Phase 1 — Technical Brainstorm (repeat for each resolved story)
-
Find the plugin's installed workflow directory, then load
AGENT.mdandPROMPT.mdfrom it (+ project overrides):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
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.
- 5d ago First seen · 52 lines · 49 tokens per session scan B e43cafb76157
StartDev is a command published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 23d ago), licensed MIT. It adds 49 tokens to every session and 1,119 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
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
init
Install the formatters this repository needs, with every command visible before it runs.
setup
Fetch Kobiton credentials from the authenticated MCP server and write them to /.kobiton/.credentials.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
adr
Create an Architecture Decision Record in memory-bank BACKLOG.