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 d-o-hub/github-template-ai-agents --skill dist-channel-selectiongit clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsWrote 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/d-o-hub/github-template-ai-agents/dist-channel-selection)<a href="https://agentmods.dev/skills/d-o-hub/github-template-ai-agents/dist-channel-selection"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/dist-channel-selection/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/d-o-hub/github-template-ai-agents/dist-channel-selection"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/dist-channel-selection.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.00063 | $0.00653 |
| Opus 5 | $0.00032 | $0.00327 |
| Sonnet 5 | $0.00013 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
dist-channel-selection 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 8d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Distribution Channel Selection
Ensure artifacts are published to the correct channels with appropriate verification.
When to Use
- User asks to publish or release a new version of a package
- Need to select the correct distribution channel (npm, Cargo, etc.)
- Even if they just say "publish this" or "release it"
Decision Matrix
| Artifact Type | Channel | Primary Verification | Dry Run Command |
|---|---|---|---|
| Rust library | crates.io | cargo test |
cargo publish --dry-run |
| WASM library | npm | scripts/wasm_size_gate.sh |
npm pack --dry-run |
| CLI (Node) | npm | npm test |
npm pack --dry-run |
| CLI (Rust) | GitHub/npm | scripts/quality_gate.sh |
cargo build --release |
Preconditions
- Version bumped in
VERSIONfile. -
CHANGELOG.mdupdated with new version details. -
./scripts/quality_gate.shpasses locally. - All CI checks are green.
Publishing Process
1. Verification
Run the domain-specific verification tools (e.g., WASM size gates, LOC enforcement).
2. Dry Run
Always perform a dry run before the final publish to catch packaging issues.
3. Final Publish
Use the official toolchain for the selected channel.
Common Pitfalls
- Publishing WASM binaries without size verification.
- Forgetting to sync the
VERSIONfile across sub-packages. - Incomplete CHANGELOG leading to consumer confusion.
See Also
cicd-pipeline— CI/CD pipeline for publishinggit-github-workflow— Git workflow for releases
Rationalizations
| Rationalization | Reality |
|---|---|
| "I'll skip the dry run — the publish always works." | Dry runs catch packaging errors, missing files, and metadata issues that silently corrupt published artifacts. |
| "The VERSION file doesn't need to match package.json." | Version mismatches confuse consumers, break CI/CD pipelines, and invalidate changelog entries. |
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.
- 8d ago First seen · 82 lines · 63 tokens per session scan A 6ecadccc396a
dist-channel-selection is a skill published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 653 once invoked, about $0.0003 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
omh-deploy-and-monitor
This is a Hermes-native deploy-and-monitor workflow skill.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…
release-notes
Draft user-facing release notes from a git log range. Trigger when the user asks for "release notes", "changelog entry", or "what shipped this week" with a git ref range. Output is markdown sections grouped by Features / Fixes / Breaking with PR links.
github
Use when automating GitHub issues, pull requests, reviews, CI checks, labels, releases, or engineering collaboration loops through the GitHub CLI.
finalize
Finalize orphaned recordings - stop processes, compress, push to orphan branch. TRIGGERS - finalize recording, stop asciinema, orphaned recording.