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 skills add Evyasys-Software-Solutions/EvyaGovernance --skill evyasys-updategit 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/skills/evyasys-software-solutions/evyagovernance/evyasys-update)<a href="https://agentmods.dev/skills/evyasys-software-solutions/evyagovernance/evyasys-update"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-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/skills/evyasys-software-solutions/evyagovernance/evyasys-update"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-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.00064 | $0.00453 |
| Opus 5 | $0.00032 | $0.00227 |
| Sonnet 5 | $0.00013 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
evyasys-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 12d 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.
What it actually says
evyasys:Update
Updates the Evyasys plugin and manages context compression with explicit user consent.
What it does
- Shows current plugin version vs latest on GitHub + changelog highlights.
- Always checks compression state — reads
~/.evyasys/settings.jsonand asks:- If enabled: Update / Keep / Disable
- If disabled: Enable / Keep disabled
- If not configured: Enable / Skip
- Acts on user's compression choice (update engine, enable, disable, or leave unchanged).
- Shows 3 commands to complete the plugin update.
Nothing about the plugin directories is touched — /plugin update owns that cleanly.
Project config, credentials, docs, board artefacts, and ~/.evyasys/settings.json are
only written when the user explicitly chooses a compression action.
For a broken install (commands missing after Update), run
/evyasys:Repair.
Compression persistence
Compression preference is stored in ~/.evyasys/settings.json:
{
"compress": {
"enabled": true,
"version": "1.2.3",
"updated_at": "2026-06-21"
}
}
Plugin updates never modify this file. It is owned entirely by the user.
What happens after
Run these commands inside Claude Code — in order:
| Step | Command |
|---|---|
| 1 | /plugin marketplace update EvyaGovernance |
| 2 | /plugin update evyasys@EvyaGovernance |
| 3 | /reload-plugins |
Then fully quit Claude Code and reopen it.
Usage
/evyasys:Update
No arguments needed.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 60 lines · 64 tokens per session scan A 5bb67d7fe71f
evyasys-update is a skill published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 453 once invoked, about $0.0003 per session on Opus 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 skills, from other repositories
michel-cli-demo-recorder
Produce proof-of-execution demos of the Packmind CLI (packmind-cli) as terminal-styled images (colors and formatting preserved exactly), for embedding in a GitHub PR. Renders a crisp master SVG and rasterizes it to a PNG — the PNG is what you embed, because GitHub does not render SVG in PR/issue bodies. Use this…
product-analytics
Product analytics and growth expert. Use when designing event tracking, defining metrics, running A/B tests, or analyzing retention. Covers AARRR framework, funnel analysis, cohort analysis, and experimentation.
api-design
REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.
manage-schemas
Creates, views, edits, deletes, and validates note schemas for the MCP Task Orchestrator in .taskorchestrator/config.yaml — the templates that define which notes agents must fill at each workflow phase. Also recommends schema designs from a library of workflow patterns (autonomous coding loops, spec-driven teams…
react-best-practices
React and Next.js performance playbook distilled from Vercel Engineering guidance. Use when building, reviewing, or refactoring React/Next.js code for waterfalls, bundle size, rendering cost, and client/server data flow.
clash-doctor
A diagnostic and configuration skill for Clash Verge and Mihomo, tools that manage network proxy profiles and routing rules. It focuses on inspecting profiles, checking connectivity, switching profiles, and routing AI tools such as Claude, Codex, Cursor, or Warp.