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 usefulmove/enso --skill convert-request-to-storygit clone --depth 1 https://github.com/usefulmove/ensoWrote 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/usefulmove/enso/convert-request-to-story)<a href="https://agentmods.dev/skills/usefulmove/enso/convert-request-to-story"><img src="https://agentmods.dev/badge/skills/usefulmove/enso/convert-request-to-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/usefulmove/enso/convert-request-to-story"><img src="https://agentmods.dev/badge/skills/usefulmove/enso/convert-request-to-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.00044 | $0.01158 |
| Opus 5 | $0.00022 | $0.00579 |
| Sonnet 5 | $0.00009 | $0.00232 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
convert-request-to-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 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Load this skill automatically when a user request exhibits ANY of these patterns:
- No explicit acceptance criteria: "Fix the bug" / "Add validation" / "Make it faster"
- No scope boundaries: "Refactor the auth system" / "Clean up the codebase"
- No verification plan: "Implement OAuth" / "Set up CI"
- Imperative, not declarative: "Do X" instead of "X should work like Y"
- Open-ended goals: "Improve the API" / "Make the dashboard look better"
- Multiple unrelated tasks in one request
This skill is a workflow skill. Run it, then follow its output.
Workflow
Step 1: Decompose
Restate the user's intent. Break multi-part requests into atomic tasks. Create a separate story for each.
If the request contains multiple tasks:
Task 1: Implement Google OAuth login
Task 2: Add session timeout logic
Task 3: Write tests for auth flow
→ Create 3 stories. Do not combine them.
Step 2: Transform Each Task Into a Story
For each atomic task, fill out the enso story template by asking clarifying questions or inferring from context:
What to Ask the User
| Vague Request | Questions to Ask |
|---|---|
| "Fix the bug" | "What is the error message? What file or page triggers it? What should happen instead?" |
| "Add validation" | "On which input fields? What are the valid vs invalid values? Should errors stop submission or just warn?" |
| "Refactor X" | "Why does X need refactoring? What tests should pass before and after? What behavior must NOT change?" |
| "Make it faster" | "Which operation is slow? What speedup is acceptable? What's the current benchmark?" |
| "Implement Y" | "What does Y do? Who uses it? What's the input/output contract? Are there existing examples to follow?" |
What to Infer From Context
Some answers come from the codebase, not the user:
- Existing style → match it
- Existing test patterns → follow them
- Existing architecture → grow incrementally
- Build/test commands → read
package.json,Makefile, CI config, orCLAUDE.md
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 · 140 lines · 44 tokens per session scan A b3daf73c5ef2
convert-request-to-story is a skill published in the GitHub repository usefulmove/enso (2 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 1,158 once invoked, about $0.0002 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
last30Days
Resolve "last30Days" to a concrete ISO date range relative to your run time — a rolling 30-day window ending today. Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a "last 30 days" / trailing-month task…
thisQuarter
Resolve "thisQuarter" to a concrete ISO date range relative to your run time — this quarter so far (quarter start → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a quarter-to-date task (QTD…
thisWeek
Resolve "thisWeek" to a concrete ISO date range relative to your run time — this week so far (Monday → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a week-to-date task (this week's activity…
harness
A meta-skill for designing and maintaining a project harness: a coordinated set of specialist agents, skills, and project instructions. It defines their roles, connects them to the project, and updates the setup as the work changes.
md-hive-sync
Munder Difflin hive sync — runs the start-of-task hive protocol steps: reads memory.md, checks inbox/ for new messages, and reminds you to record durable facts in memory.md and write coordination files before ending. Use when asked to "sync with the hive", "check my inbox", "hive status", or "hive sync". Proactively…
md-fetch-summarize
Fetch a URL and return a concise markdown summary of its content. Read-only: no files are written; the summary is returned as output only. Use when asked to "fetch and summarize", "summarize this URL", "what does this page say", or "get the content of ". Proactively suggest when the user pastes a URL and asks what it…