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-finish-devgit 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-finish-dev)<a href="https://agentmods.dev/skills/evyasys-software-solutions/evyagovernance/evyasys-finish-dev"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-finish-dev/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-finish-dev"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-finish-dev.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.00086 | $0.00499 |
| Opus 5 | $0.00043 | $0.00249 |
| Sonnet 5 | $0.00017 | $0.00100 |
| Haiku 4.5 | $0.00009 | $0.00050 |
Grade A, and why
evyasys-finish-dev 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
Skill: evyasys-finish-dev
A sign-off gate — not a rubber stamp. Every AC must have an identifiable test before this skill produces a Dev Summary. Evidence is required before claims.
What it checks
| Gate | Requirement |
|---|---|
| AC coverage | Every AC → named test file + test name → unit / integration / E2E |
| CHECKLIST.md | Every item must pass: code completeness, architecture compliance, code quality, domain-specific, process, architect gate |
| Diff scope | Files outside expected story scope flagged with severity |
| Debug markers | No console.log, print, breakpoints, TODO/FIXME in production paths |
| Docs to update | "Docs to update" table filled for 6 project docs — "Yes" rows must be scheduled |
If any AC has no test, a question is asked one at a time to resolve it before proceeding. An unresolved AC is a blocker — dev summary is not produced until the gap is acknowledged.
Dev Summary structure
The Dev Summary is the QA team's starting document. It must include:
- Files touched — path + reason for every changed file
- Tests added / updated — test file + test name → which AC it covers
- AC coverage table — one row per AC: ✅ Pass / ❌ Missing / ⚠️ Manual only
- Diff scope check — Risk / Severity / Notes for files outside expected scope
- Risks / known issues — anything QA should probe first
- Manual QA hints — edge cases, unusual flows, anything from the brainstorm
- Docs to update — which of the 6 project docs need updating after this PR
Output
.evyasys/board/**/<StoryID>/<StoryID>_DevSummary.md- ADO state → Ready for QA
- Teams handoff card posted
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 · 41 lines · 86 tokens per session scan A 997b8c4fde9d
evyasys-finish-dev is a skill published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 499 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
x-qa-gate
A quality-review gate for completed development tasks. It checks the code against the request, design, tests, verification evidence, and current changes, using different review rounds for different risk levels.
test-audit
Audit test suites for T1-T4 violations using AST analysis, mock detection, and multi-stage synthesis. Invoke when user asks to audit tests, check test quality, find mock violations, review test effectiveness, or inspect test suites for over-mocking. Triggers automatic rewrites when quality gates fail.
x-verify
A fact-checking gate that reruns the automated checks listed for a development task and reports which checks passed, failed, or still need a person. It is one step in a larger development process.
trw-audit
Adversarial spec-vs-code audit. Verifies implementation against PRD acceptance criteria, runs mandatory NFR checklist, assesses test quality. Independent from the implementer to break confirmation bias. Use: /trw-audit PRD-CORE-055.
Pair Programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.