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/no-session/claude-code-skills/factorynpx skills add no-session/claude-code-skills --skill factorygit clone --depth 1 https://github.com/no-session/claude-code-skillsWrote 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/no-session/claude-code-skills/factory)<a href="https://agentmods.dev/skills/no-session/claude-code-skills/factory"><img src="https://agentmods.dev/badge/skills/no-session/claude-code-skills/factory.svg" alt="Measured on agentmods" 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 | $0.00043 | $0.01342 |
| Opus 5 | $0.00022 | $0.00671 |
| Sonnet 5 | $0.00009 | $0.00268 |
| Haiku 4.5 | $0.00004 | $0.00134 |
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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note: This is an example showing how Factory configured the generic product-management skill with their company's Notion documents. Use this as a reference for how to customize the skill for your own organization.
Skill: Factory Product Management
Purpose
Assist with product management work at Factory by providing access to our foundational product documents, frameworks, and team context. This skill points you to the source of truth documents that should guide all product work.
When to use this skill
- Writing or reviewing PRDs and product specs
- Working on design documents
- Discussing feature prioritization
- Planning product work
- Understanding team ownership and pod structure
- Referencing product principles or positioning
Source of Truth Documents
IMPORTANT: Always fetch these Notion documents to get the latest content. These are the authoritative sources for Factory's product approach.
Core Product Philosophy
-
Product Principles — Our foundational beliefs about how we build product https://www.notion.so/309cd0f922e881f48253f1914812c501
-
Core Value Proposition — What we uniquely offer https://www.notion.so/309cd0f922e8812795a0fd8e9e3d6b28
-
11-Star Experience — Our vision for the ideal user experience https://www.notion.so/309cd0f922e881aa8c0ee8df7752abe8
-
Product Positioning — How we position ourselves in the market https://www.notion.so/309cd0f922e881ca8415d7739f481335
How We Work
-
How We Build — Our approach to building product https://www.notion.so/309cd0f922e881148107ca925ce76709
-
Prioritization Framework — How we decide what to build https://www.notion.so/309cd0f922e881919011cf9dd5d06e66
-
Product Research Bets — Our current research areas and bets https://www.notion.so/309cd0f922e881939402cb359c3360d3
Templates & Current Plans
- PRD Template — Use this template when writing PRDs https://www.notion.so/309cd0f922e8817f812cc2fba8261095
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 · 130 lines · 43 tokens per session scan A 8fc5a4e09cf2
factory is a skill published in the GitHub repository no-session/claude-code-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 1,342 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…