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-standupnpx skills add nonlinear-xyz/factory-kit --skill factory-standupgit 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-standup)<a href="https://agentmods.dev/skills/nonlinear-xyz/factory-kit/factory-standup"><img src="https://agentmods.dev/badge/skills/nonlinear-xyz/factory-kit/factory-standup.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.1 | $0.00022 | $0.00584 |
| Opus 5 | $0.00011 | $0.00292 |
| Sonnet 5 | $0.00004 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
factory-standup 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 6d 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 giving the user a dev-standup view of their open Linear work in this project. The goal is to answer "what's in flight, what's the top priority, what's waiting?" without making them open Linear in a browser.
What to do
-
Read project configuration. Prefer
.factory-kit/linear.json. If it is absent, read legacy.claude/linear.jsonas a migration fallback and tell the user to run the setup-linear workflow to migrate. If neither exists, stop and direct the user to setup-linear. -
Resolve scope. Pull
teamIdfrom the config. IfprojectIdis present, scope to that project; otherwise stay team-wide. -
List open issues through the connected Linear integration:
team: <teamId>project: <projectId>(if present in config)statefiltered to open states only (excludeDone,Completed,Cancelled,Duplicate)- Sort by priority (Urgent → High → Normal → Low), then by updated date desc
-
Return a tight status (≤ 300 words):
Project: name + active milestone if present, or just team name if no project scope
In progress — issues in
In Progress(or whatever the team's equivalent active state is). One line per issue:<TEAM-N> — title (assignee if not me).In review — issues in
In Review. Same format. Surface stale ones (> 3 days).Top priority (next up) —
UrgentandHigh-priority open issues not yet started. Order by priority then update date. Show 5–8.Backlog — count + a sample of 3–5 from
Todo/Backlogstates, prioritized.Blocked (only if any) — issues with open
blockedBy. Show what's blocking each.One-line recommendation: the single best issue to pick up next, given priority and blockers. Cite the portable entry workflow with
<TEAM-N>; in Claude, preserve the compatibility form/entry <TEAM-N>.
Style
Follow factory-voice.md. Tight, glanceable lines — the user is scanning for a decision, not reading a report. Don't reprint full descriptions; titles only. Always cite issue IDs in canonical form (e.g., NON-45). The recommendation at the end is a call, not a suggestion — name the reason in one clause ("highest priority, no blockers" / "in review > 3 days, unblock the reviewer first").
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.
- 6d ago First seen · 39 lines · 22 tokens per session scan A 6a3da653f322
factory-standup is a skill published in the GitHub repository nonlinear-xyz/factory-kit (9 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 584 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
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-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.
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.
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…
upstream-tracker
Manage upstream issue tracking for this project. Use when the user wants to log a bug or friction point in a vendor package or npm dependency, review open upstream items, resolve a tracked issue, run a trend review, generate the upstream observations section of a sprint retrospective, promote upstream observations to…