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 jjdmev2/dme-skills --skill storythisgit clone --depth 1 https://github.com/jjdmev2/dme-skillsWrote 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/jjdmev2/dme-skills/storythis)<a href="https://agentmods.dev/skills/jjdmev2/dme-skills/storythis"><img src="https://agentmods.dev/badge/skills/jjdmev2/dme-skills/storythis/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/jjdmev2/dme-skills/storythis"><img src="https://agentmods.dev/badge/skills/jjdmev2/dme-skills/storythis.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.00237 | $0.02594 |
| Opus 5 | $0.00118 | $0.01297 |
| Sonnet 5 | $0.00047 | $0.00519 |
| Haiku 4.5 | $0.00024 | $0.00259 |
Grade A, and why
storythis 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 11d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
storythis
You just finished a design (a feature, a redesign, a spec — on a branch, in a doc, or in this very session) and now you're handing it to the dev team to build. Your job is to land it in Linear as the right structure — no code — so a dev who wasn't in the room can pick it up cold, and a lead can prioritize.
This is NOT /linearthis. /linearthis shapes a fuzzy idea into an Epic-issue → sub-issues tree for the
person who'll build it themselves (then /ccthis). /storythis is the designer→dev handoff of already-
designed work, with heavier conventions: value-framed Projects, a shared design issue as the source of
truth, and lean, code-verified build stories. If the user actually wants to brainstorm a raw idea, point
them to /linearthis (or gstack /office-hours) first.
Work the phases in order. Each is independent — if a tool or step fails, do the rest and say so; never
silently skip. Never write code. Requires the Linear MCP (/mcp to log in).
Phase 0 — Right-size the structure (the adaptive core — do this first)
Do NOT assume "project + design issue + stories." Decide what actually fits, and default to the lightest structure that does the job. Derive from the input; ask only what you genuinely can't infer.
| Situation | Create |
|---|---|
| A whole feature/area, several stories, wants an owner-facing home + prioritization | Project (epic) + design issue + build stories |
| A self-contained change (fits one PR, a couple of ACs) | One issue (fold design + build) — no project, no separate design issue |
| The design already lives somewhere (a design issue, a doc, a branch) | Skip creating a design issue — point the stories' blockedBy at the existing one |
| A project already exists for this area | Add to it — don't make a duplicate (list_projects to find it) |
| Just capturing rough ideas / a wishlist | Backlog issues only, Low priority, each marked "idea / needs design / not critical" |
| Two+ distinct sub-areas (e.g. Users vs Groups) | Two projects sharing one design issue (stories blockedBy it cross-project is fine) |
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.
- 11d ago First seen · 170 lines · 237 tokens per session scan A 5aefb78d7b5b
storythis is a skill published in the GitHub repository jjdmev2/dme-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 237 tokens to every session and 2,594 once invoked, about $0.0012 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
recipe-decompose
Decomposes Linear issues or requirement documents into the fewest implementation-ready value units, then registers the approved tasks in Linear. Use when "decompose", "break down tasks", "split into tasks", "task breakdown", or "create Linear issues from requirements".
codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…
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.