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 bybren-llc/a-safe-pulse --skill agent-coordinationgit clone --depth 1 https://github.com/bybren-llc/a-safe-pulseWrote 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/bybren-llc/a-safe-pulse/agent-coordination)<a href="https://agentmods.dev/skills/bybren-llc/a-safe-pulse/agent-coordination"><img src="https://agentmods.dev/badge/skills/bybren-llc/a-safe-pulse/agent-coordination/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/bybren-llc/a-safe-pulse/agent-coordination"><img src="https://agentmods.dev/badge/skills/bybren-llc/a-safe-pulse/agent-coordination.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.00054 | $0.01055 |
| Opus 5 | $0.00027 | $0.00528 |
| Sonnet 5 | $0.00011 | $0.00211 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
agent-coordination 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 4d 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.
This is a copy
100% identical to agent-coordination — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Coordination Skill
TEMPLATE: This skill uses
{{PLACEHOLDER}}tokens. Replace with your project values before use.
Purpose
Guide correct agent assignment, blocker escalation, and delivery coordination following the TDM role boundaries.
When This Skill Applies
- Assigning work to specialist agents
- Managing blockers across agents
- Coordinating multi-agent workflows
- Escalating issues to ARCHitect/POPM
- Verifying pre-implementation gate
- Updating ticket system with evidence
Stop-the-Line Conditions
FORBIDDEN Patterns
# FORBIDDEN: Wrong agent assignment
Database work -> BE Developer # WRONG: Use Data Engineer!
Security validation -> QAS # WRONG: Use Security Engineer!
Documentation -> BE Developer # WRONG: Use Tech Writer!
# FORBIDDEN: Skipping pre-implementation gate
Start coding before BSA spec # Must have acceptance criteria first
# FORBIDDEN: Unresolved blockers >4 hours
Blocker exists but not escalated # Escalate within 1 hour
CORRECT Patterns
# CORRECT: Right agent for the job
Database work -> Data Engineer
Security validation -> Security Engineer
Documentation -> Tech Writer
Planning/Specs -> BSA
Architecture review -> System Architect
API implementation -> BE Developer
UI implementation -> FE Developer
Testing -> QAS
PR/Release -> RTE
Agent Assignment Matrix (MANDATORY)
| Work Type | Correct Agent | Never Use |
|---|---|---|
| Database/Migrations | Data Engineer | BE Developer |
| Security/RLS | Security Engineer | QAS |
| Documentation | Tech Writer | BE/FE Developer |
| Specs/Planning | BSA | Any implementation |
| Architecture | System Architect | Direct to developer |
| API Routes | BE Developer | FE Developer |
| UI Components | FE Developer | BE Developer |
| Testing/QA | QAS | Implementation team |
| PR/Releases | RTE | Developers |
What ships with it
3 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.
- 4d ago First seen · 169 lines · 54 tokens per session scan A c719d1d75b65
agent-coordination is a skill published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 1,055 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-coordination, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.