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 cafitac/codex-channels --skill channels-demogit clone --depth 1 https://github.com/cafitac/codex-channelsWrote 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/cafitac/codex-channels/channels-demo)<a href="https://agentmods.dev/skills/cafitac/codex-channels/channels-demo"><img src="https://agentmods.dev/badge/skills/cafitac/codex-channels/channels-demo.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.00023 | $0.00086 |
| Opus 5 | $0.00012 | $0.00043 |
| Sonnet 5 | $0.00005 | $0.00017 |
| Haiku 4.5 | $0.00002 | $0.00009 |
Grade A, and why
channels-demo 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 7d 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
channels-demo
Use this skill when you want to create a real interaction. Run the command first, handle approval/escalation if port binding is required, then guide the user toward pending and reply-latest.
Preferred command:
codex-channels demo
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.
- 7d ago First seen · 14 lines · 23 tokens per session scan A e8988410b15c
channels-demo is a skill published in the GitHub repository cafitac/codex-channels (2 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 86 once invoked, about $0.0001 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
memorywhale
Query and write durable debugging memory recorded by MemoryWhale. Use when debugging a failure that may have happened before, when you need the exact error/flags/output from an earlier attempt, when the user asks "how did we fix this last time?", or once you've figured out why something failed / how a fix worked and…
tree-ring-memory
Guides AI agents in using Tree Ring Memory for durable recall, project decisions, user preferences, warnings, future seeds, privacy-safe memory capture, and lifecycle-aware forgetting.
model-router
Score a coding task and route it to a cheap, mid, or premium model tier before spending tokens. Use at the start of any coding, review, debug, or planning request on any agent host (Cursor, Codex, Claude Code, Gemini, Kimi, Herdr, etc.). Prefer Otito agentexperience (AX) when available; otherwise use the heuristic…
otito-context
Run otito context before editing — task-aware primary files, tests, patterns, and validation commands. Invoke explicitly before planning or implementing a change.
otito-review
Run otito review and gate before merge — composite verdict, PR context, and PASS/WARN/FAIL checks. Invoke before declaring a PR merge-ready.
otito-scope
Scope a change before implementation — impact ranking, AX score, and adversarial questions. Invoke when the task is ambiguous or blast radius matters.