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 zekker6/claude-code-channel-matrix --skill configuregit clone --depth 1 https://github.com/zekker6/claude-code-channel-matrixWrote 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/zekker6/claude-code-channel-matrix/configure)<a href="https://agentmods.dev/skills/zekker6/claude-code-channel-matrix/configure"><img src="https://agentmods.dev/badge/skills/zekker6/claude-code-channel-matrix/configure.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.00032 | $0.00510 |
| Opus 5 | $0.00016 | $0.00255 |
| Sonnet 5 | $0.00006 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
configure 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 6d 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 6d ago First seen · 57 lines · 32 tokens per session scan A 420e70abed96
configure is a skill published in the GitHub repository zekker6/claude-code-channel-matrix (4 stars, last pushed today), with no licence file. It adds 32 tokens to every session and 510 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-08-31.
Other skills, from other repositories
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
tools-unity-unitask
UniTask async/await patterns for Unity including cancellation, lifecycle binding, and coroutine interop.
tools-unity-vcontainer
VContainer dependency injection patterns for Unity including lifecycle management, scoped registrations, and common pitfalls.
api-design
Use when designing or reviewing a public API surface — REST/GraphQL/gRPC, versioning, idempotency, error contracts, pagination, auth boundary. Helps choose between transport styles and avoid breaking-change footguns.
api-design
Designs REST, GraphQL, and gRPC APIs (OpenAPI/schema/proto output) and reviews existing APIs for consistency, best practices, and breaking change risks.
architecture-design
Designs new systems from requirements: C4 model diagrams, service boundaries, API contracts, data design, failure modes, and cross-cutting concerns.