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 richfrem/agent-plugins-skills --skill user-story-capturegit clone --depth 1 https://github.com/richfrem/agent-plugins-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/richfrem/agent-plugins-skills/user-story-capture)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/user-story-capture"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/user-story-capture/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/richfrem/agent-plugins-skills/user-story-capture"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/user-story-capture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00094 | $0.01350 |
| Opus 5 | $0.00047 | $0.00675 |
| Sonnet 5 | $0.00019 | $0.00270 |
| Haiku 4.5 | $0.00009 | $0.00135 |
Grade A, and why
user-story-capture 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Story Capture
Derive structured user stories and acceptance criteria from exploration session captures.
Usage
python ./scripts/execute.py \
--input <file> [<file2>...] \
--format <standard|gherkin> \
--output <output_file.md>
Formats:
standard(default):As a [user type], I want [goal], so that [benefit]— with priority table and gaps.gherkin: Standard +Given / When / ThenAcceptance Criteria blocks per story.
Flags:
--input PATH [PATH ...]: Session brief, BRD draft, prototype notes, or prior captures--output PATH: Destination file (default:exploration/captures/user-stories-draft.md)--format FORMAT: Output format (default:standard)
Interactive Co-Authoring Workflow
When invoked interactively, follow this 3-stage pattern. Do not dump a full story list at once.
Stage 1: Context Gathering
Ask all three questions in a single message before generating anything:
- Input files: Which source documents should I work from? (Check
exploration/— list what you find: session brief, BRD draft, prototype notes.) If no files exist, stop and ask for input before proceeding. - Primary actor: Which user role, system actor, or job-to-be-done is the highest priority for the first implementation slice? (Use role-neutral language — e.g., "the person approving requests", "the agent running evals", not just "the user".)
- Out-of-scope: Are there any actors or workflows we should explicitly exclude from this story set?
- Format: Should acceptance criteria use standard format (
As a / I want / So that) or Gherkin (Given / When / Then)? Default to standard unless Gherkin is requested.
After the user responds: read each input file they identify.
Stage 2: Iterative Refinement
Build the backlog in layers — do not jump straight to full Gherkin blocks.
- Outline first: Based on the input files and primary actor, present a numbered list of lightweight story titles (one line each, no ACs yet). Ask: "Which of these should we keep, cut, or merge for the first slice?"
- Curate: Apply changes. Mark any story derived from unclear or inferred source material as
[UNCONFIRMED]. - Draft approved stories: For each kept story, write the full format:
- Standard:
As a [actor], I want [goal], so that [benefit]. - Gherkin: Add
Given / When / ThenAC blocks after the story statement.
- Standard:
What ships with it
6 files 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.
- 7d ago First seen · 100 lines · 94 tokens per session scan A 99d544090114
user-story-capture is a skill published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 1,350 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
composio
Use Composio from Agent Swarm through the agent-swarm x composio CLI route, the swarmx MCP tool, or a registered ctx.api.composio script connection. Trigger when a task needs connected third-party app tools such as Gmail, Google Calendar, Google Docs, Google Drive, GitHub, Slack, Notion, or HubSpot through Tool Router…
close-issue
Close a GitHub or GitLab issue with a summary comment.
soul
Embody this digital identity. Read SOUL.md first, then STYLE.md, then examples/. Become the person—opinions, voice, worldview.
implement-issue
Implement a GitHub issue or GitLab issue and create a PR/MR.
bbc-skill
A read-only tool for collecting all comments from a Bilibili video, including replies and pinned comments. Bilibili is a Chinese video-sharing platform.
feature-implementation
Implement software features, fix bugs, and write production-quality code. Use this for hands-on development work including writing new code, modifying existing code, and debugging issues.