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 commands/nonlinear-xyz/factory-kit/setup-lineargit clone --depth 1 https://github.com/nonlinear-xyz/factory-kitWhat 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.00012 | $0.00051 |
| Opus 5 | $0.00006 | $0.00026 |
| Sonnet 5 | $0.00002 | $0.00010 |
| Haiku 4.5 | $0.00001 | $0.00005 |
Grade A, and why
setup-linear 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 2d 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
Load and follow the canonical factory-setup-linear skill. It owns discovery, legacy-config migration, validation, and the write to .factory-kit/linear.json.
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.
- 2d ago First seen · 7 lines · 12 tokens per session scan A 12486dac3d36
setup-linear is a command published in the GitHub repository nonlinear-xyz/factory-kit (9 stars, last pushed 28d ago), licensed MIT. It adds 12 tokens to every session and 51 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 commands, from other repositories
get-to-work
Autonomous ops work. Args: [mode] [repeat]. Modes: tasks | opps | full | escalating (default). Repeat: cycle (keep going, default) | once (single pass). Run this before stepping away from an ops repo.
recap
Summarize what happened in the project since a given date. Produces a short lead on what's different now, backed by tables and lists covering completed work, state changes, backlog movement, and key decisions. Use when the user wants to catch up on project activity, review recent progress, or generate a status update…
whats-next
Generate an executive overview of the project. Synthesizes state, backlogs, and recent plans into a ranked action plan answering "What should we do next?".
forge-status
Show registry of all managed projects with scores, trends, and alerts.
constitution
根据交互输入或已提供原则创建或更新项目章程，并确保相关模板保持同步。.
set-tracker
Set the issue tracker for the current project.