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 Eigenwise/eigenwise-toolshed --skill user-storygit clone --depth 1 https://github.com/Eigenwise/eigenwise-toolshedWrote 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/eigenwise/eigenwise-toolshed/user-story)<a href="https://agentmods.dev/skills/eigenwise/eigenwise-toolshed/user-story"><img src="https://agentmods.dev/badge/skills/eigenwise/eigenwise-toolshed/user-story.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 298 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00177 | $0.04538 |
| Opus 5 | $0.00088 | $0.02269 |
| Sonnet 5 | $0.00035 | $0.00908 |
| Haiku 4.5 | $0.00018 | $0.00454 |
Grade A, and why
user-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 7d 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
user-story
A guided path from "build me X" to integrated, verified work on main. Two ideas run through all of
it:
The orchestrator holds the plan; executors hold the code. It is the most expensive model in the loop and the worst implementer available, because its context is the scarcest resource in the system. Judging plans is its job. Writing and reviewing diffs is not.
The ceremony scales to the work. A three-proposal design panel and a five-lens review are right for a subsystem that changes an on-disk format, and pure waste for a new CLI flag. You decide the size, you state it, and every step below reads off that decision.
Board mechanics live in the sidequest skill (claim lifecycle, dispatch fields, routing, publish
transaction) and its references/. Read ../sidequest/references/orchestration.md before a first
wave. This skill is the sequence and the sizing, not a second copy of those rules.
Size it first
Sizing is a call you make and state in a line, not a question you ask the user. Read these signals:
- Independently checkable pieces: one, a handful, or many.
- Surfaces crossed: one module, or store plus CLI plus MCP plus UI plus hooks plus docs.
- Reversibility: a schema, migration, on-disk format, wire format, or public API is expensive to undo. Internal helpers are not.
- Is the approach contested? More than one defensible architecture, with real trade-offs between them, is the single strongest reason to run a design panel.
- Blast radius: does existing behavior change for people already using this?
- Stakes: data loss, auth, money, the release path itself.
Three sizes, and what each dial does at each:
| Dial | One ticket | One wave | Multi-wave |
|---|---|---|---|
| Recon | inline Read/Grep/Explore |
plus one exploration ticket when the seam is unclear | 2-3 parallel exploration tickets on distinct angles |
| Questions | none, state assumptions | one batched round if a contract-changing call exists | one batched round, expect a real decision |
| Design | write the contract yourself | one planning or spike ticket when the approach is open | 2-3 competing proposals, judged and merged into one contract |
| Backlog | one ticket, no story | story plus the wave's full backlog | story plus the full backlog for every wave, dependency-linked |
| Execution | one executor | one parallel wave | wave after wave, re-planned between |
| Review | the done-oracle | oracle plus one review-audit when the oracle is thin |
a review panel with distinct lenses, by default |
| Integration | integrate and close | integrate the wave, full suite once | integrate per wave, full suite per wave, decisions logged between |
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.
- 7d ago First seen · 333 lines · 177 tokens per session scan A 091ab333694a
user-story is a skill published in the GitHub repository Eigenwise/eigenwise-toolshed (37 stars, last pushed yesterday), licensed MIT. It adds 177 tokens to every session and 4,538 once invoked, about $0.0009 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.