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/update)<a href="https://agentmods.dev/commands/evyasys-software-solutions/evyagovernance/update"><img src="https://agentmods.dev/badge/commands/evyasys-software-solutions/evyagovernance/update/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/update"><img src="https://agentmods.dev/badge/commands/evyasys-software-solutions/evyagovernance/update.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.00045 | $0.00608 |
| Opus 5.5 | $0.00018 | $0.00243 |
| Sonnet 5.5 | $0.00009 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
Update scanned grade A with 0 findings 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 1mo 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running /evyasys:Update.
Step 1 — Explain what will happen
Tell the user:
- The command checks your current plugin version against the latest on GitHub and shows what's new
- After confirming, you will also be asked about context compression (update / enable / disable / keep)
- Then you will be shown 3 commands to run to complete the plugin update
.evyasys/docs, board artefacts,project.yaml, and~/.evyasys/credentialsare never touched- If commands are still missing or broken after updating, run
/evyasys:Repair
Step 2 — Ask for plugin update confirmation
Ask the user to confirm they want to proceed with the plugin update before doing anything else.
Stop here until the user confirms.
Step 3 — Check compression state and ask
Use the Read tool to read ~/.evyasys/settings.json (ignore error if file does not exist).
Show the user their current compression status and ask one clear question:
If compress.enabled is true:
Context compression: ✅ Enabled (v
{compress.version})What would you like to do? (U) Update — upgrade the compression engine to the latest version (K) Keep — leave it as-is (D) Disable — turn off compression
If compress.enabled is false:
Context compression: ❌ Disabled
(E) Enable — install and activate compression (requires Python 3.8+) (K) Keep disabled — leave it off
If ~/.evyasys/settings.json does not exist or has no compress key:
Context compression: ⚙️ Not configured on this machine
(E) Enable — install and activate compression (requires Python 3.8+) (S) Skip — configure later via
/evyasys:Update
Wait for the user's answer.
Step 4 — Output markers
Output exactly these two lines and nothing else after them.
Choose the compress marker based on the Step 3 answer:
| User chose | Marker |
|---|---|
| Update / Enable | <!-- EVYACOMPRESS update --> |
| Disable | <!-- EVYACOMPRESS disable --> |
| Keep / Skip | <!-- EVYACOMPRESS skip --> |
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.
- 1mo ago First seen · 68 lines · 45 tokens per session scan A 74705b66a9fe
Update is a command published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 17d ago), licensed MIT. It adds 45 tokens to every session and 608 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
brain
Set up or use your Professional Brain — init, ingest, recall, or review.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
plan
Turn an approved spec into an implementation plan an engineer with zero context could execute — with a quality controller that blocks placeholders and hollow tasks.
init
Install the formatters this repository needs, with every command visible before it runs.
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.
audit
Onboard an existing codebase: every domain's checks over the whole tree, then a triaged plan to bring it in line.