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-delivergit 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-deliver)<a href="https://agentmods.dev/skills/evyasys-software-solutions/evyagovernance/evyasys-deliver"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-deliver/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-deliver"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-deliver.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.00264 | $0.01146 |
| Opus 5 | $0.00132 | $0.00573 |
| Sonnet 5 | $0.00053 | $0.00229 |
| Haiku 4.5 | $0.00026 | $0.00115 |
Grade A, and why
evyasys-deliver 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: evyasys-deliver
What it does
End-to-end story orchestrator that runs 10 phases with 3 human approval gates:
| Phase | Action | Autonomous? |
|---|---|---|
| 0 | Batch-load story + subtasks + rules + all quality-gate docs + templates | Yes |
| 1 | Codebase probe + batch clarifying questions (Gate 1 — auto-skipped if none) | Gate |
| 2 | Architecture reference scan + brainstorm recommendation (Gate 2) | Gate |
| 3 | Write the code following every loaded standard | Yes |
| 4 | Full ReviewDev self-review with up to 2 auto-fix iterations | Yes |
| 5 | Generate test plan (positive/negative/edge/regression/non-functional) | Yes |
| 6 | Queue doc updates for TrainDocs --retrain |
Yes |
| 7 | Draft DevSummary + ReleaseNotes | Yes |
| 8 | Final approval summary (Gate 3 — commit + PM update + notify) | Gate |
| 9 | Hook: writes artefacts, creates feature branch, local commit, PM update, notification | Yes |
| 10 | Per-story status report + next steps | Yes |
What it produces per story
4 artefacts (never 5 — release notes belong to FinishQa) written to .evyasys/board/**/<StoryID>/:
| Artefact | Purpose |
|---|---|
<id>_TechBrainstorm.md |
The approved architecture decision + reference files |
<id>_DevSummary.md |
ACs met, files touched, tests added, manual QA hints, docs to update, assumptions |
<id>_CodeReview.md |
Full self-review with severity-graded findings + verifier fact-check result |
<id>_TestPlan.md |
AC-driven test cases including edge and regression |
Plus:
- PM state transitioned to Ready for QA
- One notification per story (or per epic in epic mode)
- Traceability entry appended to
.evyasys/traceability.json .evyasys/CONTEXT.mdregenerated- No git operations (default) — source-code changes are in the working tree, developer commits + pushes
- With
--commit: hook additionally creates the feature branch and a local commit (never pushed)
Speed targets (from AGENT.md)
| Story size | Target wall time |
|---|---|
| Small (1–3 subtasks, ≤ 5 files) | < 5 min |
| Medium (4–7 subtasks, 6–15 files) | < 15 min |
| Large (8+ subtasks, 15+ files) | < 30 min (announced up-front with offer to split) |
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 · 71 lines · 264 tokens per session scan A 380d4d3e2346
evyasys-deliver is a skill published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 1mo ago), licensed MIT. It adds 264 tokens to every session and 1,146 once invoked, about $0.0013 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
product-manager-toolkit
Use when the user needs product management workflows such as RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, go-to-market strategy, feature prioritization, research synthesis, or requirements documentation.
weekly
A weekly-report workflow that combines Git history with records from Claude Code and Codex sessions. It turns work from a selected date range into a report for two related software repositories.
review-proposals
Triages pending improvement-proposal MCP items — presents each with its scope and evidence, collects an accept/reject/defer decision per proposal, and carries out the disposition: project-scoped acceptances get their exact YAML applied to .taskorchestrator/config.yaml and pushed per-root; global acceptances get a…
work-summary
Generates a project dashboard from MCP work items. Default is a lean, attention-first view: what's in flight, what's blocked, what to do next, what's queued. Use when the user says: project status, what's active, show me the dashboard, work summary, what should I work on, project health, what's blocked, where did I…
adopt-project-scope
Migrates an already-populated, unscoped Task Orchestrator database in place to the project-scoping convention — creates a project anchor root, re-parents existing work trees under it, and writes rootId back to config.yaml. Use when a user says: adopt project scope, migrate this database to project scoping, make this…
batch-complete
Completes or cancels multiple items at once — closes out features, cleans up old work, and archives completed workstreams. Use when a user says: close out this feature, complete everything under X, cancel this workstream, clean up old items, bulk complete, finish this feature, or archive completed work.