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 agentmods add skills/bostonorange/claude-code-framework/draft-storynpx skills add BostonOrange/claude-code-framework --skill draft-storygit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWhat 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 | $0.00034 | $0.01098 |
| Opus 5 | $0.00017 | $0.00549 |
| Sonnet 5 | $0.00007 | $0.00220 |
| Haiku 4.5 | $0.00003 | $0.00110 |
Grade A, and why
draft-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 2d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Story
Create complete, refined tickets from business requirements or design documents. Write for a technical audience — direct, concise, specific identifiers over display names.
When to use this vs /refine-story:
/draft-story— New requirements or design document → create new tickets/refine-story— Existing ticket that needs improvement or gap analysis
Input Sources
1. Business Requirements (ad-hoc)
User describes a business need or feature request verbally. Follow the full interview process.
2. Design Documents (pasted or fetched)
User provides a structured design document. These typically include:
- Objective / Overview
- Open Questions
- Technical Design (data flows, endpoint specs, field mappings)
- Data Model Changes
- Business Logic
- Integration Details
Design docs may cover multiple tickets — propose how to split.
Process
From business requirements:
- User describes business need
- Ask clarifying questions (Who, What, Why, When, Where)
- Explore codebase for relevant patterns
- Fetch documentation using the
/fetch-docsskill pattern (resolve-library-id then get-library-docs) when the solution involves external dependencies — verify actual API capabilities before committing to a technical approach - Propose solution options if multiple approaches exist
- Draft complete ticket
- Present open questions for stakeholder follow-up
- Save to
docs/stories/TICKET-{id}/ordocs/stories/DRAFT-{name}/
From design documents:
- User provides design document content
- Parse all sections — identify scope, TBDs, and open questions
- Clarify architecture early: sync vs async, data flow direction
- Explore codebase to verify existing components
- Identify gaps: what the doc leaves unresolved
- If doc covers multiple tickets, propose split and ask which to draft
- Draft complete ticket with design doc section references
- Surface open questions — grouped by source (doc TBDs vs codebase gaps)
- Resolve open questions interactively — work through each one
- Save to
docs/stories/TICKET-{id}/ordocs/stories/DRAFT-{name}/
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.
- 2d ago First seen · 129 lines · 34 tokens per session scan A 7c5524cbd2d7
draft-story is a skill published in the GitHub repository BostonOrange/claude-code-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,098 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
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
organize-project
Organise documents into folders and move them between folders and modules with MOVE. Use when a module has grown unstructured, when restructuring a project, or when a document is in the wrong place.
smithers-supervise
Watch for stale running runs and auto-resume them. Run smithers supervise --help for usage details.