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/nonlinear-xyz/factory-kit/factory-entrynpx skills add nonlinear-xyz/factory-kit --skill factory-entrygit clone --depth 1 https://github.com/nonlinear-xyz/factory-kitWrote 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/nonlinear-xyz/factory-kit/factory-entry)<a href="https://agentmods.dev/skills/nonlinear-xyz/factory-kit/factory-entry"><img src="https://agentmods.dev/badge/skills/nonlinear-xyz/factory-kit/factory-entry.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.00017 | $0.00756 |
| Opus 5 | $0.00009 | $0.00378 |
| Sonnet 5 | $0.00003 | $0.00151 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
factory-entry 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 4d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You're starting a focused work session on a single Linear issue. Load its context, summarize it, and enter plan mode so the user can sign off before you start coding.
Invocation input: the issue identifier. Accept either the full form (NON-45) or just the number (45). If numeric, prepend the team key from the project configuration.
What to do
-
Read project configuration. Prefer
.factory-kit/linear.json; use legacy.claude/linear.jsononly as a migration fallback. If neither exists, stop and direct the user to the setup-linear workflow. PullteamKeyfor ID resolution. -
Resolve the identifier. If the invocation input is numeric, construct
<teamKey>-<num>(e.g.,45→NON-45). If already inKEY-NNform, use it as-is. -
Fetch the issue through the connected Linear integration. Include comments and linked sub-issues if available.
-
Fetch the project through the Linear integration if the issue belongs to one and you haven't loaded it yet this session.
-
Check blockers. If the issue has open
blockedByrelations, list them and warn loudly before proceeding. Ask whether the user wants to continue or pick a different ticket. -
Summarize for context (≤ 250 words). Use this shape — bold labels, short lines, omit any section that's empty:
- Issue:
<KEY-N> — title+ priority + current state - Outcome: one sentence on what "done" observably looks like. If the issue lacks a clear outcome, say so — that's the first thing to fix.
- Scope: the unchecked acceptance criteria / open checkboxes
- Encoded constraints: anything in the description or comments that locks an approach — name the underlying force (compliance, perf budget, prior decision), not just the rule
- Customer voice: if user feedback is quoted in the issue or linked, surface the raw words — don't paraphrase
- Open design calls: "decide during build" items worth resolving up front
- Context graph: parent, sub-issues, blockedBy/blocks, linked PRs, design docs — IDs + titles only. This is the issue's place in the wider decision graph; if it looks isolated, flag it as a yellow flag.
- Issue:
-
Flag issue quality (brief — one line if everything is fine). Linear's house style is: short title with a concrete outcome, body only as long as needed. If the issue is missing a clear outcome, written as a user story, or sitting orphaned with no context links, name it. Don't fix it silently — surface it so the user can decide whether to rewrite before designing the change.
-
Enter planning mode. Use the host's planning capability when available. Otherwise, present the implementation plan in chat and stop for explicit approval. Do not start coding before approval.
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.
- 4d ago First seen · 39 lines · 17 tokens per session scan A 94c2aac9baf4
factory-entry is a skill published in the GitHub repository nonlinear-xyz/factory-kit (9 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 756 once invoked, about $0.0001 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
dev-finish
Close out a session — summarise what changed, capture what was learned, and prepare the commit.
scaffold
Set up or align a non-code ops/PM repo with the ops folder structure, CLAUDE.md, and INDEX.md hierarchy.
roadmap
· Capture, track, and prioritize ideas in gitignored ROADMAP.md. Triggers: 'roadmap', 'ideas', 'feature ideas', 'competitive analysis', 'what should I build', 'feature backlog'. Not for project management or code review.
dev-cycle
Run a feature end to end — scout the code, plan it, build it, and keep a session file so a closed terminal doesn't lose the thread.
sibling-sync
Bilateral SYNERGY/UPSTREAM reconciliation across sibling projects. Use when the user wants to sync sibling SYNERGY/UPSTREAM files, compare both sides to surface drift, find reciprocation gaps (entries here but not there, or vice versa), flag stale-aligned rows, detect status drift across sides, surface friction the…
synergy-tracker
Manage cross-project synergy tracking between sibling projects. Use when the user wants to log a shared pattern, a divergence, an extraction candidate, or something a sibling project has that this one doesn't. Also use when the user wants to promote synergy entries to Basic Memory (workflow 5). NOT for upstream…