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-create-storygit 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-create-story)<a href="https://agentmods.dev/skills/evyasys-software-solutions/evyagovernance/evyasys-create-story"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-create-story/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-create-story"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-create-story.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.00074 | $0.00869 |
| Opus 5 | $0.00037 | $0.00434 |
| Sonnet 5 | $0.00015 | $0.00174 |
| Haiku 4.5 | $0.00007 | $0.00087 |
Grade A, and why
evyasys-create-story 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: evyasys-create-story
/evyasys:CreateStory is the full feature delivery kick-off — one command creates everything needed to start building.
What it does
- Captures intent — describe requirements inline (Path A) or provide a reference document (Path B).
- Resolves epics — scans existing epics, matches themes to them, proposes new epics for unmatched themes.
- Gate 1 — confirms new epics before creating them (skipped if all epics already exist).
- Plans all stories — proposes the complete story list across all epics, with IDs, SP estimates, and key ACs.
- Gate 2 — one approval for the full batch (user can remove, rename, or adjust SP).
- Drafts every story — full
STORY_TEMPLATE.mdfill, self-review per story, cross-story consistency check. - Saves + syncs — local files first (always safe), then PM tool (ADO / JIRA / GitHub Projects), PM IDs back-written.
- Notification A — epics table: ID, Title, Status (New/Existing), PM ID.
- Notification B — stories table: ID, Title, Epic, SP, PM ID, sync status for every story (failures highlighted when they occur).
Two paths for requirements input
Path A — Describe here
The agent guides the user through structured clarifying questions one at a time.
Path B — Reference document
User provides a file path. The agent:
- Reads all provided files.
- Analyses from four perspectives: Business Analyst, Architect, Quality, Scope Decomposition (multi-epic scope only).
- Asks only the blocking questions — one at a time, with reason.
- Archives the doc + analysis + Q&A to
.evyasys/board/referencedoc/{YYYY-MM-DD}/. - Notifies user of the archive path.
- Drafts stories with a
Reference Doc:metadata line pointing to the archive.
Gates
| Gate | Fires when | What it confirms |
|---|---|---|
| Gate 1 | ≥ 1 new epic proposed | Epic IDs, titles, and goals before any file is created |
| Gate 2 | Always | Full story plan table — user can modify before drafting begins |
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 · 78 lines · 74 tokens per session scan A 72069c9febc8
evyasys-create-story is a skill published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 869 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
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…