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-repairgit 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-repair)<a href="https://agentmods.dev/skills/evyasys-software-solutions/evyagovernance/evyasys-repair"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-repair/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-repair"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-repair.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.00075 | $0.00416 |
| Opus 5 | $0.00037 | $0.00208 |
| Sonnet 5 | $0.00015 | $0.00083 |
| Haiku 4.5 | $0.00007 | $0.00042 |
Grade A, and why
evyasys-repair 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:Repair
Full clean reinstall for a broken Evyasys plugin installation.
What it does
- Asks for confirmation before touching anything.
- Clears
~/.claude/plugins/cache/EvyaGovernance. - Clears
~/.claude/plugins/marketplaces/EvyaGovernance. - Removes the evyasys plugin entry from all Claude Code settings files (user, project, local).
- Shows 4 commands to do a complete fresh reinstall from scratch.
Project config (.evyasys/project.yaml), credentials (~/.evyasys/credentials), docs, board artefacts, and memory are never touched — only plugin code is removed.
When to run it
- Commands are missing or broken after a Claude Code update.
/evyasys:Updateran but commands still don't appear.- Plugin appears installed but commands don't autocomplete.
- Any plugin-related problem that a normal update doesn't fix.
What happens after
Run these commands inside Claude Code — in order:
| Step | Command |
|---|---|
| 1 | /reload-plugins |
| 2 | /plugin marketplace add https://github.com/Evyasys-Software-Solutions/EvyaGovernance.git |
| 3 | /plugin install evyasys@EvyaGovernance |
When prompted at step 3, choose Install for you (user scope), then fully quit Claude Code and reopen it.
Usage
/evyasys:Repair
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 · 47 lines · 75 tokens per session scan A 19bd8333e6cc
evyasys-repair is a skill published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 416 once invoked, about $0.0004 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
openocd
A toolkit for programming and debugging microcontrollers through hardware probes such as ST-Link or CMSIS-DAP. OpenOCD can act as a GDB Server, allowing a debugger to inspect source code, registers, memory, breakpoints, and program execution.
jlink
A tool for using a SEGGER J-Link probe to connect a computer to an embedded chip for programming and debugging.
serial
A tool for communicating with devices over serial ports, such as USB-to-UART connections. It can find ports, watch incoming data, send messages, save logs, and display raw bytes in hexadecimal form.
eide
A build tool for EIDE projects, an embedded-development extension for Visual Studio Code. It finds EIDE project settings and builds firmware using ARM CC or GCC.
net
A toolkit for diagnosing network connections and traffic in embedded systems. A packet capture is a recorded sample of network traffic, and this tool can create or analyze captures in formats such as pcap and pcapng.
can
A debugging tool for CAN and CAN-FD, communication systems used by vehicles and embedded devices. It can find interfaces, monitor and send messages, record logs, decode DBC database files, and report bus statistics.