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/squidbay/factory/team-leadernpx skills add squidbay/factory --skill team-leadergit clone --depth 1 https://github.com/squidbay/factoryWrote 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/squidbay/factory/team-leader)<a href="https://agentmods.dev/skills/squidbay/factory/team-leader"><img src="https://agentmods.dev/badge/skills/squidbay/factory/team-leader.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.00079 | $0.00565 |
| Opus 5 | $0.00039 | $0.00282 |
| Sonnet 5 | $0.00016 | $0.00113 |
| Haiku 4.5 | $0.00008 | $0.00056 |
Grade A, and why
team-leader 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.
What it actually says
Team Leader boot — thin loader
This skill is deliberately small, and it is a snapshot: uploaded skills drift as the repo evolves, so nothing role-critical lives here. The repo is canon.
This card is now named for the seat: team-leader. Its parent folder still reads seats/cowork/ — that one is an address, not a name, and the retired-folder sweep is a later step.
On invocation:
- Read
seats/cowork/BOOT-PROMPT.mdfrom the factory repo, off livemain, in full — via the GitHub connector, not from memory of this skill. - Follow it exactly: it will send you to
seats/_shared/BOOT-COMMON.mdfirst (the boot every seat shares — read it in full; §0 is the roster), then grounding links,MECHANICAL-RULES.md,seats/cowork/OVERRIDES.md, and the top ofjournal.md— and confirm the boot per RULE 17. - If you cannot read the repo, the GitHub connector isn't connected, and a blind centre is worse than none. That becomes priority zero: walk the human through Settings → Connectors → GitHub, then verify by reading a real file and saying what you see.
Say in your first reply which file you booted from and that you read it off live main — that one sentence is how your human can tell the card was only a pointer, not the source (RULE 3).
What this card is, and what it is not. This loader is Factory-owned: it travels with the Factory, updates with it, and is deliberately kept small enough to be a contract rather than content. The boot material it points at — BOOT-PROMPT.md, GROUNDING.md, OVERRIDES.md, and anything your office adds beside them — is yours, and no Factory update overwrites it. That split is declared in .github/template-manifest.txt and enforced by the sync engine; it is why this card can keep improving while the seat behind it stays exactly as your office wrote it.
If this skill and the repo ever disagree, the repo wins — and say you noticed.
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 · 23 lines · 79 tokens per session scan A caa0e74c7851
team-leader is a skill published in the GitHub repository squidbay/factory (5 stars, last pushed 15d ago), licensed MIT. It adds 79 tokens to every session and 565 once invoked, about $0.0004 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
stage-assemble
How to execute a validated, currently authorized project/plan.json into one finished file. Start/resume with production.status; if planapprovalcurrent is false, pass the state to gate-control and stop instead of producing or opening child gates. Walk the signed EDL; do not re-plan. Host-neutral: VideoStudio-specific…
stage-plan
How to turn "here is my material + here's the video I want" into a single, inspectable plan that spans reference images, reference videos, deterministic editing, semantic editing, generation, and composition. The output is project/plan.json — a cross-modal Edit Decision List (EDL) — which the assembler walks.…
ppt-planner
Read only after ppt-router chooses CREATE or OUTLINE. Planning is the source of truth for construction, not optional prose around the deck.
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.
image-compose
Read this skill after route lock for COMPOSE, or later in HYBRID, GENERATE, or EDIT only when deterministic copy, layout, diagram, framing, crop, mask, or overlay work is required. Do not preload it during routing. Keep the artifact in one stable directory containing image-manifest.json, index.html, and local assets.
image-router
Read this skill first and alone for every image creation or revision request. Return a locked route before reading any other ImageStudio skill; do not batch this read with craft, canvas, production, or review skills.