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 Eliyce/paqad-ai --skill story-and-solution-writergit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/story-and-solution-writer)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/story-and-solution-writer"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/story-and-solution-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/skills/eliyce/paqad-ai/story-and-solution-writer"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/story-and-solution-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.00016 | $0.00507 |
| Opus 5 | $0.00008 | $0.00253 |
| Sonnet 5 | $0.00003 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
story-and-solution-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 12d 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.
What it actually says
What It Does
Produces implementation-ready story and solution prose that ties problem framing, constraints, approach, and verification together without collapsing into code-level detail.
Use This When
Use this when requirements and sequence exist but the execution artifact still needs a clear narrative that engineering, review, and documentation work can all follow.
Inputs
- Read the enriched requirements, acceptance criteria, and current sequence plan.
- Read the closest canonical docs and any stack-specific guidance for the affected surface area.
- Read
references/story-template.mdbefore drafting the artifact.
Procedure
- Summarize the user or business problem in one paragraph grounded in the request.
- State the constraints, dependencies, and non-goals that shape the solution.
- Describe the proposed approach in ordered steps that explain the workflow goal without writing code.
- Tie each major approach decision back to acceptance or verification needs.
- List documentation or rollout work that must happen alongside implementation.
Output Contract
- Match
assets/output.template.md:## Story,## Constraints,## Proposed Solution,## Verification Notes. Optional## Pending Decisionswhen applicable. - Each section must trace back to the request, not invent rollout or migration steps unsupported by the known system context.
- Output must pass
scripts/lint-output.sh(exit 0).
Escalate / Stop Conditions
- Ask when the approach depends on an unresolved architecture choice or cross-team dependency.
- Warn when the requested scope is too broad for one coherent story artifact.
- Do not invent rollout or migration steps that are not supported by the known system context.
Resources
references/story-template.mdscripts/lint-output.shassets/output.template.mdruntime/base/skills/acceptance-criteria-gen/SKILL.mdagents/openai.yaml
What ships with it
4 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.
- 12d ago First seen · 68 lines · 16 tokens per session scan A d061bc604507
story-and-solution-writer is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 507 once invoked, about $0.0001 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
pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer…
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
auto-go
A command that implements code from a SPEC, a document describing the required behavior and work.
auto-plan
A code-planning skill that examines a codebase and creates a detailed specification, implementation plan, and acceptance criteria. It can organize requirements using EARS, a structured way to describe how software should behave in different situations.
agent-pipeline
Multi-agent pipeline orchestration skill.
adaptive-quality
Per-task execution profile selection based on complexity in Balanced quality mode.