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 dbc-oduffy/coordinator-claude --skill cloud-channelgit clone --depth 1 https://github.com/dbc-oduffy/coordinator-claudeWrote 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/dbc-oduffy/coordinator-claude/cloud-channel)<a href="https://agentmods.dev/skills/dbc-oduffy/coordinator-claude/cloud-channel"><img src="https://agentmods.dev/badge/skills/dbc-oduffy/coordinator-claude/cloud-channel/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/dbc-oduffy/coordinator-claude/cloud-channel"><img src="https://agentmods.dev/badge/skills/dbc-oduffy/coordinator-claude/cloud-channel.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.00017 | $0.01014 |
| Opus 5.5 | $0.00007 | $0.00406 |
| Sonnet 5.5 | $0.00003 | $0.00203 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
cloud-channel 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 9d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 9d ago Changed · -2 lines d4ca06ee77a8
- 19d ago Changed · +5 lines 703e40c8fba3
- 24d ago Changed · -7 tokens per session 2a39ec0dfb07
- 28d ago Changed · -4 tokens per session 0880dffeaf28
- 1mo ago Changed · +7 lines 7a2837668182
- 1mo ago First seen · 47 lines · 28 tokens per session scan A 713571e259b3
cloud-channel is a skill published in the GitHub repository dbc-oduffy/coordinator-claude (6 stars, last pushed 3d ago), with no licence file. It adds 17 tokens to every session and 1,014 once invoked, about $0.0001 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-09-24.
Other skills, from other repositories
upstream
Opt-in upstream contribution workflow for process improvements and field lessons. Scans the consuming repo's local AGENTS.md, {{ agentsdir }}/team.toml, and commit history for emergent rules, sanitizes sensitive client context, formats governed rule origins, and drafts an upstream Pull Request or Issue to the upstream…
pr-feedback
Work a reviewer's comments on a pull request to the end - all three comment surfaces enumerated before any is triaged, every comment fixed, declined with a reason, or ticketed, push before you reply. Use when a PR comes back with review feedback or a red check.
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
stack-pr
Use when breaking a too-big branch into a stack of smaller chained PRs — commit-based default, --smart agent-reshape, gh-stack detection, cross-links. Invoked by /orc:stack-pr and /orc:ship's size gate.
init
Opt-in onboarding for the mARC agent team. Scaffolds a per-repo team binding so the team graduates from ephemeral session-memory to persistent, versioned config — without ever writing a file silently. Discovers the repo's org/repo/ project at runtime via gh, prefills {{ agentsdir }}/team.toml, and (optionally) a lean…
tech-lead
Channel operator (IRC handle @techlead) for the mARC agent team. Compiles chat demands into ready-to-execute work, records them on the GitHub Project board/Issues, and dispatches to specialists (@dev, @sre, @design, @sec, @rev, @research). Invoke with /tech-lead to turn discussion into tracked, delegated tasks.