Borrowing it
Nothing to install: this file belongs to bybren-llc/rendertrust. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bybren-llc/rendertrust/dev/.claude/skills/agent-coordination/SKILL.mdgit clone --depth 1 https://github.com/bybren-llc/rendertrustWrote 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/rendertrust/agent-coordination)<a href="https://agentmods.dev/skills/bybren-llc/rendertrust/agent-coordination"><img src="https://agentmods.dev/badge/skills/bybren-llc/rendertrust/agent-coordination.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.00033 | $0.01086 |
| Opus 5 | $0.00016 | $0.00543 |
| Sonnet 5 | $0.00007 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00109 |
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 2d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Coordination Skill
Purpose
Guide correct agent assignment, blocker escalation, and delivery coordination following the TDM role boundaries.
When This Skill Applies
Invoke this skill when:
- Assigning work to specialist agents
- Managing blockers across agents
- Coordinating multi-agent workflows
- Escalating issues to ARCHitect/POPM
- Verifying pre-implementation gate
- Updating Linear 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
# CORRECT: Pre-implementation gate
1. BSA creates spec with acceptance criteria
2. System Architect reviews patterns
3. THEN specialist executes
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
1 file 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.
- 2d ago First seen · 180 lines · 33 tokens per session scan A 13676e90eee0
agent-coordination is a skill published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,086 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.