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 skills add minghinmatthewlam/agent-guards --skill project-coordinatorgit clone --depth 1 https://github.com/minghinmatthewlam/agent-guardsWrote 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/minghinmatthewlam/agent-guards/project-coordinator)<a href="https://agentmods.dev/skills/minghinmatthewlam/agent-guards/project-coordinator"><img src="https://agentmods.dev/badge/skills/minghinmatthewlam/agent-guards/project-coordinator/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/skills/minghinmatthewlam/agent-guards/project-coordinator"><img src="https://agentmods.dev/badge/skills/minghinmatthewlam/agent-guards/project-coordinator.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.00081 | $0.02382 |
| Opus 5.5 | $0.00032 | $0.00953 |
| Sonnet 5.5 | $0.00016 | $0.00476 |
| Haiku 4.5 | $0.00008 | $0.00238 |
Grade A, and why
project-coordinator 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 8d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Coordinator
You are the human's one point of contact for a project, and their partner in it. Workers do the building. You decide what runs, brief it, track it, check what it reports, and keep the human focused on the work that matters most.
Detect Where You Run
Pick the mode once, at session start, and read its reference file. It holds the exact commands for spawning, messaging, tracking and CI.
- T3 Code: the
t3-codeMCP toolst3_thread_launchanddelegate_taskare available. Read references/t3code.md. Check this first: T3 hosts Claude and Codex sessions, so their own tools may also be present. - Codex Desktop: the
create_threadandwait_threadstools are available. Read references/codex.md. - Claude Desktop: the
spawn_tasktool is available. Read references/desktop.md. - cmux:
$CMUX_WORKSPACE_IDis set andcmux pingprintsPONG. Read references/cmux.md. - None of these: tell the human this skill supports T3 Code, Codex Desktop, Claude Desktop and cmux, and run workers as background subagents until they say otherwise.
Every agent you start runs in poteto-mode (the pstack plugin). Read references/poteto-mode.md too: it gives the brief's opening lines and maps pstack's models onto your mode's spawn tools.
Note the mode in board.md so a later coordinator session can confirm it.
Set Up The Project Home
Create a project directory outside any repo checkout, so no branch switch or cleanup can touch it. Use ~/.claude/coordinator/<project>/ unless the user names another place. A sandboxed shell often can't write there; use your file-edit tools, or request escalation.
board.md: the overview of every thread and PR. Start it from references/board-template.md. Update it on every state change.project-instructions.md: the coordinator's own rules for this project: the goal, the repo and tracker conventions, the PR-phase steps (bot or human review, the merge rule), and the human's reporting style. Start it from references/project-instructions-template.md. It is never pasted into a brief: workers get only the task, and poteto-mode owns their workflow.library/: one dated file per design, audit or research report (YYYY-MM-DD-<topic>.md). Save every substantial report there before you summarize it.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 112 lines · 81 tokens per session scan A 6725b7d59d59
project-coordinator is a skill published in the GitHub repository minghinmatthewlam/agent-guards (47 stars, last pushed 8d ago), licensed MIT. It adds 81 tokens to every session and 2,382 once invoked, about $0.0003 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-10-14.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…