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-diagnosegit 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-diagnose)<a href="https://agentmods.dev/skills/evyasys-software-solutions/evyagovernance/evyasys-diagnose"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-diagnose/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-diagnose"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-diagnose.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.00179 | $0.00647 |
| Opus 5 | $0.00089 | $0.00324 |
| Sonnet 5 | $0.00036 | $0.00129 |
| Haiku 4.5 | $0.00018 | $0.00065 |
Grade A, and why
evyasys-diagnose 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 11d 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
Skill: evyasys-diagnose
Purpose
Detect drift, misconfiguration, credential expiry, or corrupted state before a delivery command hits them. Report actionable fixes. Never modify state.
What it checks (20 checks across 6 areas)
| Area | Checks | Notes |
|---|---|---|
| Plugin install (1–5) | Plugin dir resolves · commands present · skills present · workflows present · compression engine | Uses the same locator every delivery command uses |
| Project config (6–9) | project.yaml valid · credentials decrypt · PM tool configured · notification tool configured |
Verifies AES-256-GCM v2 decryption round-trip |
| Integrations reachability (10–12) | PM API reachable · notification webhook DNS · compression MCP registered | Fast-fail on unreachable — no long retries in a diagnostic run |
| Docs & memory (13–16) | Universal docs present · docs freshness (90d / 180d thresholds) · CONTEXT.md present · functional docs | Age thresholds surface stale docs before they cause bad brainstorms |
| Board consistency (17–18) | Every story has _UserStory.md · ado-map covers every synced story |
Detects orphaned board entries |
| Git state (19–20) | In git repo · default branch detected | Same detection Deliver uses (origin/HEAD → main → master) |
Output
Human-readable report with per-check PASS/WARN/FAIL/SKIP + summary tally + issues-to-address list.
Also emits a structured <!-- EVYADIAGNOSE { ... } --> tail block that the hook uses for a
one-liner tally.
What it does NOT do
- Never writes to
.evyasys/ - Never edits
project.yaml - Never rotates credentials
- Never posts a test notification
- Never runs a PM state transition
- Never fixes anything automatically — reports what needs fixing, tells you the command to run
Usage
/evyasys:Diagnose
Run before demos, after a plugin update, when a delivery command is behaving unexpectedly, or on a periodic health-check cadence.
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.
- 11d ago First seen · 49 lines · 179 tokens per session scan A d8779f746fe2
evyasys-diagnose is a skill published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 29d ago), licensed MIT. It adds 179 tokens to every session and 647 once invoked, about $0.0009 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.
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.
task-graph
Execute an approved multi-task plan as a verified DAG with @taskgraph — parallel squad workers per task, validation gates the engine runs itself, and an independent reviewer verdict before any task counts as done. Use for deliveries of 5+ tasks with real independence between them; for smaller work dispatch workers…