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-setup-linearnpx skills add nonlinear-xyz/factory-kit --skill factory-setup-lineargit 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-setup-linear)<a href="https://agentmods.dev/skills/nonlinear-xyz/factory-kit/factory-setup-linear"><img src="https://agentmods.dev/badge/skills/nonlinear-xyz/factory-kit/factory-setup-linear.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.00031 | $0.00596 |
| Opus 5 | $0.00015 | $0.00298 |
| Sonnet 5 | $0.00006 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
factory-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 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You're configuring this project to use the Factory Kit Linear workflows. The other workflows read .factory-kit/linear.json from the project root; this workflow creates or migrates it.
What to do
-
Check for configuration. Read
.factory-kit/linear.json. If it exists, show the current contents and ask whether the user wants to overwrite, edit, or abort. If it is absent but legacy.claude/linear.jsonexists, use that as a migration fallback, show it, and offer to write the equivalent canonical file. -
Discover Linear context. Use the connected Linear integration's available capabilities:
- List teams the user can access. Show
key — name (id)lines. - Ask which team to use through the host's user-interaction capability, or directly in chat when no structured prompt exists. Capture both
key(e.g.,NON) andid(UUID). - List projects filtered to the chosen team. Ask whether standup should be scoped to one active project; "no" means team-wide.
- If a project is chosen, capture
idandname.
- List teams the user can access. Show
-
Confirm state names. Defaults are
"In Review"and"Done". List issue statuses for the chosen team through the Linear integration and verify both names exist. If not, ask the user for the actual names. -
Write
.factory-kit/linear.jsonwith this shape:{ "teamKey": "NON", "teamId": "<uuid>", "projectId": "<uuid-or-omit>", "projectName": "<name-or-omit>", "states": { "inReview": "In Review", "done": "Done" }, "branchPattern": "<owner>/<teamKey-lower>-<number>-<topic>" }projectId/projectNameare optional — omit the keys entirely if the user didn't pick a project.branchPatternis documentation-only —/submitand/closeparse the branch with a regex (-(\d+)-) and don't depend on this string. Include it so future readers know the convention.
-
Show the file path and confirm — print "Wrote .factory-kit/linear.json. Factory Kit's standup, entry, submit, and close workflows are ready." Don't commit it; the user decides whether to check it in.
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 · 44 lines · 31 tokens per session scan A 0971e8aea823
factory-setup-linear is a skill published in the GitHub repository nonlinear-xyz/factory-kit (9 stars, last pushed 29d ago), licensed MIT. It adds 31 tokens to every session and 596 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
prompt-sensei
Stage-aware prompt coaching, prompt improvement, lookback analysis, prompting habit feedback, and local reports about prompt quality for AI coding agents such as Claude Code or Codex.
agent-template
Generate custom agent from template. Use when creating a new subagent from scratch, or scaffolding an agent file with correct frontmatter.
skill-template
Generate custom skill/command from template. Use when creating a new skill or slash command from scratch, or scaffolding a skill file with correct frontmatter.
check-environment
Verify Claude, Codex, and Grok availability plus Director guidance, relay, agents, and skills. Audit optional hooks only when selected. Use after installation or when a native surface misbehaves.
doc-writer
Documentation templates and standards: README structure, API reference format, changelog (Keep a Changelog), and comment guidelines. Use when creating or updating documentation. Loaded automatically by the doc-writer agent.
smart-commit
Create clean Conventional Commits: inspect the diff, group related changes, run quality checks, and write type(scope) messages. Use when committing work, or when the user runs /smart-commit or asks to commit changes.