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/factorynpx skills add BostonOrange/claude-code-framework --skill factorygit 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.00046 | $0.02015 |
| Opus 5 | $0.00023 | $0.01007 |
| Sonnet 5 | $0.00009 | $0.00403 |
| Haiku 4.5 | $0.00005 | $0.00201 |
Grade A, and why
factory 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 yesterday.
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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Factory
End-to-end AI Software Factory: readiness → develop → PR → CI deploy to test environment.
Usage
/factory TICKET-1234
/factory 1234
Overview
The factory pipeline automates the full path from an approved ticket to code deployed in a test environment for review. It chains existing skills with factory-mode defaults that eliminate manual decision points.
Human Touchpoints (reduced from 5+ to 2)
- Architect/PM drafts ticket —
/draft-storyresolves all open questions → ticket is "Ready for Sprint" - Code review — reviewer approves PR. Code is already deployed in test environment (by CI).
- Smoke test — users validate in staging after auto-deploy
Everything else is automated.
Architecture
Developer Terminal (Claude Code) │ CI/CD (automatic)
─────────────────────────────────────┼──────────────────────────────────
│
/factory TICKET-xxx │
├─ /check-readiness │
├─ Create worktree + branch │
├─ Scaffold + implement │
├─ /validate (code standards only) │
├─ Fix code standards issues │
├─ Commit + push │
├─ Create PR (factory label) ─────┼──► CI validate workflow
└─ /improve (background) │
│ ├─ Deploy to test environment
│ ├─ Run tests
│ └─ Post PR comment with env link
│
Review ─┼──► Reviewer tests in environment
│
PR Approved ──┼──► CI auto-merge workflow
│
PR Merged ──┼──► CI deploy workflow
│ ├─ Deploy to staging
│ ├─ Notify team
│ └─ Update ticket state
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.
- yesterday First seen · 259 lines · 46 tokens per session scan A 8b292a6f4a39
factory is a skill published in the GitHub repository BostonOrange/claude-code-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 2,015 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…