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 owainlewis/blueprint --skill factorygit clone --depth 1 https://github.com/owainlewis/blueprintWrote 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/owainlewis/blueprint/factory)<a href="https://agentmods.dev/skills/owainlewis/blueprint/factory"><img src="https://agentmods.dev/badge/skills/owainlewis/blueprint/factory/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/owainlewis/blueprint/factory"><img src="https://agentmods.dev/badge/skills/owainlewis/blueprint/factory.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.00053 | $0.00368 |
| Opus 5.5 | $0.00021 | $0.00147 |
| Sonnet 5.5 | $0.00011 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
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 3d 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
Factory
Take the provided GitHub issue to a pull request. Do not ask the user anything.
Work in a new git worktree at ../<repo>-<issue>, on a new branch from the latest
default branch. Put the issue number in the branch name, such as 42-fix-login.
Keep the repository's branch prefix if it has one.
- Review the provided issue and write a PRODUCT_SPEC.md and a TECHNICAL_SPEC.md
in
docs/<feature-slug>/. - Implement TECHNICAL_SPEC.md, with a test for each requirement in PRODUCT_SPEC.md.
- Run the tests and fix any failures. Check that each new test fails without your change.
- Open a pull request. Start its description with
Closes #<issue>, then add three sections: What changed, Why, and Verification. - Wait for CI with
gh pr checks --watch. Fix any failures and push. - If recent pull requests in the repository have automated reviews, wait up to 10 minutes for them. Fix each comment, or reply with why not. If you pushed a fix, go back to step 5.
- Comment on the issue with the pull request link and what happened.
Stop after 3 rounds of CI or review fixes. Never weaken a test, merge, or force-push.
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.
- 3d ago First seen · 30 lines · 53 tokens per session scan A b7ffa545bb5b
factory is a skill published in the GitHub repository owainlewis/blueprint (410 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 368 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-10-01.
Other skills, from other repositories
speq-implement-pr
Headless follow-up to /speq-plan-pr. Continues a plan on its feat/plan-name branch and runs it end-to-end: implements via /speq-implement, bumps the version, commits and pushes, runs the real test suites, records only if green, then opens/updates the PR and marks it ready. Resumes from the PR Lifecycle checkpoint in…
verify-before-complete
Block completion claims until verification evidence has been produced in the current message. Use before marking a task/slice/milestone complete, before creating a commit or PR, before saying "it works" or "tests pass", and any time you are about to claim work is done. The rule is: evidence before claims, always …
release-archivist
Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.
precommit
Pre-commit checks — lint:fix -> build -> test.
ship-workflow
Automated release pipeline: merges main, runs tests, pre-landing review, version bump, changelog, bisectable commits, and PR creation. Triggers on: "ship it", "release this", "prepare for release", "open a PR", "push and PR", "land this", "/ship-workflow".
precommit-fast
Quick pre-commit checks — lint:fix -> test.