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 check-readinessgit 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/check-readiness)<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/check-readiness"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/check-readiness/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/check-readiness"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/check-readiness.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.00043 | $0.01171 |
| Opus 5.5 | $0.00017 | $0.00468 |
| Sonnet 5.5 | $0.00009 | $0.00234 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
check-readiness 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Readiness
Automated readiness gate — validates a ticket is implementation-ready before entering /develop.
Usage
/check-readiness TICKET-1234
/check-readiness 1234
Purpose
20-30% of tickets arrive in /develop needing major refinement, causing the dev cycle to halt. This skill runs automated checks to catch gaps early and return structured feedback before development starts.
Phase 1: Fetch Ticket Content
Parse ticket ID from input.
{{TRACKER_FETCH_TICKET}}
Extract:
- Title
- Description (story body, tech spec, field mappings)
- Acceptance Criteria
- Test instructions
- Deployment notes / tech spec
Also check local docs if they exist: docs/stories/TICKET-{id}/story.md
Phase 2: Run Readiness Checks
Check 1: No Placeholder Text (FAIL)
Scan all content for:
TBD,TBC,TBA(case-insensitive)TODOoutside of code blocks[placeholder]or{placeholder}patterns???or...used as placeholders
Check 2: Data Model Completeness (FAIL)
For each data/field reference in the ticket:
- Identify the entity and field
- Look up existing definitions in the codebase
- Verify the referenced values are valid (enum values, types, relationships)
Check 3: Testable Acceptance Criteria (WARN)
Scan each AC for vague language:
- "should update" without specifying from/to values
- "appropriate" without defining what qualifies
- "relevant" without listing which items
- "as needed" without conditions
- "properly" or "correctly" without measurable criteria
Check 4: No Unresolved Open Questions (FAIL)
Scan for:
- "Open Questions" section with unresolved items
- Items marked with
?,OPEN, or no answer - Comments with unanswered questions
Check 5: Explicit Technical Specs (FAIL)
Scan for:
- Vague references: "the field on the account", "the status field"
- Missing API names / identifiers
- Incomplete mappings: source specified but no target
Check 6: Integration Contracts (WARN)
If the ticket involves integrations, check for:
- Payload structure defined
- Endpoint specified
- Authentication documented
- Error handling specified
- Retry strategy documented
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 · 171 lines · 43 tokens per session scan A fa4a9f5bf5f6
check-readiness is a skill published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 1,171 once invoked, about $0.0002 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…