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-start-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-start-dev)<a href="https://agentmods.dev/skills/evyasys-software-solutions/evyagovernance/evyasys-start-dev"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-start-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-start-dev"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-start-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.00165 | $0.00444 |
| Opus 5 | $0.00082 | $0.00222 |
| Sonnet 5 | $0.00033 | $0.00089 |
| Haiku 4.5 | $0.00016 | $0.00044 |
Grade A, and why
evyasys-start-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 10d 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-start-dev
Phase 1 — Technical Brainstorm
Loads the story and subtasks. Runs a repo scan. Generates at least 3 distinct implementation approaches (each with pros, cons, estimate delta). Recommends one with a clear deciding reason. Waits for team to agree before proceeding.
The brainstorm is saved to the story folder under .evyasys/board/ — it travels
with the PR so the architectural decision is on record.
Phase 2 — Start-Dev Gates
| Gate | Check |
|---|---|
| Subtasks | .evyasys/board/**/<id>/subtasks/<id>_Subtasks.md exists and is non-empty |
| Branch | matches feature/<id>-<kebab> naming convention |
| Draft PR | confirmed open (via gh or user confirmation) |
| Definition of Ready | re-checked line by line against current story |
| Dependencies | each story dependency confirmed cleared |
Produces a gate table with GO / NO-GO verdict.
Output
.evyasys/board/**/<StoryID>/<StoryID>_TechBrainstorm.md— agreed technical plan- ADO state → In Progress
- Teams kickoff 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.
- 10d ago First seen · 34 lines · 165 tokens per session scan A 644f4f4e7a62
evyasys-start-dev is a skill published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 28d ago), licensed MIT. It adds 165 tokens to every session and 444 once invoked, about $0.0008 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.
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…
linear
Manage Linear issues from the terminal via the official GraphQL API and the user's API key — list/search issues, create issues, update status/assignee, add comments. Use when asked to "create a Linear issue", "what's assigned to me in Linear", "move this issue to done", "comment on LIN-123".
lov-rename-project
A project-renaming workflow that updates a product or repository name across source files, configuration, and documentation. It produces a reviewable plan and preserves compatibility-sensitive names and references where needed.
lov-repo2docs
Turn any folder of source material — a code repository, a pile of articles, a mixed knowledge dump with images — into a professional, polished Fumadocs (Next.js) documentation website, then deploy it to https://{product-id}.example.com/docs. Works by reading the folder one unit at a time and incrementally growing and…