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.
git 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/commands/nonlinear-xyz/factory-kit/entry)<a href="https://agentmods.dev/commands/nonlinear-xyz/factory-kit/entry"><img src="https://agentmods.dev/badge/commands/nonlinear-xyz/factory-kit/entry/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/commands/nonlinear-xyz/factory-kit/entry"><img src="https://agentmods.dev/badge/commands/nonlinear-xyz/factory-kit/entry.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.00014 | $0.00074 |
| Opus 5.5 | $0.00006 | $0.00030 |
| Sonnet 5.5 | $0.00003 | $0.00015 |
| Haiku 4.5 | $0.00001 | $0.00007 |
Grade A, and why
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 1mo 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-entry skill. Pass $ARGUMENTS as its invocation input. Do not begin implementation until the workflow's planning approval gate is satisfied.
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.
- 1mo ago First seen · 8 lines · 14 tokens per session scan A 261a07af7c57
entry is a command published in the GitHub repository nonlinear-xyz/factory-kit (9 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 74 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.
workpm-mcp
A project-manager mode that coordinates independent AI workers through MCP, a standard way for tools and programs to exchange tasks and results. It supports task-based work across compatible command-line tools.
pmworker
A worker mode for a multi-agent project coordinator. It takes assigned coding tasks, works within specified files, and uses results from earlier tasks.
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…
forge-status
Show registry of all managed projects with scores, trends, and alerts.