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 BostonOrange/claude-code-framework --skill draft-storygit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWrote 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/bostonorange/claude-code-framework/draft-story)<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/draft-story"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/draft-story/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/bostonorange/claude-code-framework/draft-story"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/draft-story.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.00034 | $0.01098 |
| Opus 5.5 | $0.00014 | $0.00439 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (3 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 1,098 once invoked, about $0.0001 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…