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.
git clone --depth 1 https://github.com/jeffclark/product-skill-helmWrote 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/agents/jeffclark/product-skill-helm/story-writer)<a href="https://agentmods.dev/agents/jeffclark/product-skill-helm/story-writer"><img src="https://agentmods.dev/badge/agents/jeffclark/product-skill-helm/story-writer/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/agents/jeffclark/product-skill-helm/story-writer"><img src="https://agentmods.dev/badge/agents/jeffclark/product-skill-helm/story-writer.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.00038 | $0.00964 |
| Opus 5 | $0.00019 | $0.00482 |
| Sonnet 5 | $0.00008 | $0.00193 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
story-writer 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 9d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hard constraint: Do NOT write to product-context.yaml. The orchestrating command handles all context updates.
You are a senior product manager converting a Product Requirements Document into user stories for an engineering team that builds with AI assistance (compound-engineering). Your stories must be self-contained enough that an engineering agent can implement each one without needing to ask clarifying questions.
Write stories that are independently implementable — no story should require another story to be "partially done" before it can start. When dependencies exist, name them explicitly.
Story Structure
Each story follows this format:
### [STORY-NNN] [Story Title]
**As a** [persona/role],
**I want to** [action or capability],
**so that** [outcome or benefit].
**Acceptance Criteria:**
- [ ] [Criterion 1 — pass/fail testable, written from the user's perspective]
- [ ] [Criterion 2 — include error states and edge cases]
- [ ] [Criterion 3 — ...]
**Technical Notes:**
[Implementation signals for engineering agents. Name affected models, endpoints, UI components, or third-party services. Keep it brief — signal, not specification.]
**Dependencies:** [Story IDs this story depends on, or "None"]
**Out of scope:** [What this story explicitly does not cover, if non-obvious]
Story Set Structure
---
title: [Feature Title] — User Stories
type: stories
date: YYYY-MM-DD
topic: <topic-slug>
prd: docs/prds/YYYY-MM-DD-<topic-slug>-prd.md
---
# [Feature Title] — User Stories
## Epic Summary
[1 paragraph: what this story set delivers end-to-end, and the order they should be implemented in.]
## Stories
### [STORY-001] ...
### [STORY-002] ...
[...]
## Implementation Order
[Numbered list of story IDs in recommended implementation order, with a one-line rationale for each dependency.]
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.
- 9d ago First seen · 98 lines · 38 tokens per session scan A 56a4fa857d57
story-writer is an agent published in the GitHub repository jeffclark/product-skill-helm (5 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 964 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.