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-subtaskgit 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-subtask)<a href="https://agentmods.dev/skills/evyasys-software-solutions/evyagovernance/evyasys-create-subtask"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-create-subtask/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-subtask"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-create-subtask.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.00130 | $0.01274 |
| Opus 5 | $0.00065 | $0.00637 |
| Sonnet 5 | $0.00026 | $0.00255 |
| Haiku 4.5 | $0.00013 | $0.00127 |
Grade A, and why
evyasys-create-subtask 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: evyasys-create-subtask
/evyasys:CreateSubtask decomposes one story or an entire epic's worth of stories in a single run.
What it does
- Resolves inputs — expands epic IDs to all their story IDs; deduplicates
- Loads all story files in one batch — extracts ACs and Impacted Areas per story
- Builds shared knowledge base once — quality-gate docs from
.evyasys/docs/(or derived from codebase if docs absent); union of all domain docs based on all stories' flags - Unified code analysis — unions all impacted areas, reads each file once; builds shared technical inventory
- Cross-story dependency analysis — shared files, shared infrastructure tasks, sequence requirements, parallelism opportunities, merge-conflict risk
- Single Gate — consolidated plan table (all stories, strategy, task count, cross-story notes) — one approval for the whole batch
- Drafts all subtasks — functional headlines + business rules + AC Coverage Map + Data Flow + Error & Recovery + deep Technical Guidance per task, using shared context (no re-reading); no code in any task; maximum 5 tasks per story (4 implementation + 1 QA)
- Shared task handling — tasks serving multiple stories written once in the owning story; reference entries in others
- Cross-story consistency check — every AC covered, no contradictions across shared files, QA regression rows cover cross-story touchpoints
- Saves and syncs (progressive) — two modes:
- Story input: each story is saved locally → PM-synced → notified immediately before moving to the next
- Epic input: all stories in the epic are saved locally first, then PM-synced together, then a single notification fires for that epic; the next epic starts immediately after
- Playwright spec scaffolding — one spec file per story from QA test scenarios
- Notifications —
subtasks-batch-createdfires per story (story mode) or per epic (epic mode) — never waits for the entire batch to complete
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 · 105 lines · 0 tokens per session scan A 56f89e01516d
evyasys-create-subtask is a skill published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 28d ago), licensed MIT. It adds 130 tokens to every session and 1,274 once invoked, about $0.0006 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…