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 agentmods add skills/codeinfinity1/stram/channel-operationsnpx skills add CodeInfinity1/Stram --skill channel-operationsgit clone --depth 1 https://github.com/CodeInfinity1/StramWhat 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 | $0.00021 | $0.01062 |
| Opus 5 | $0.00010 | $0.00531 |
| Sonnet 5 | $0.00004 | $0.00212 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
channel-operations 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Channel Operations
Tool Map
channel_catalogchannel_manifestchannel_setup_requirementschannel_setup_savechannel_setup_statuschannel_doctorchannel_integration_smokechannel_listener_statuschannel_listener_tickchannel_webhook_ingestchannel_message_preparechannel_action_preparechannel_message_sendchannel_outbox
Use this skill when the task involves onboarding, diagnosing, or sending through any chat channel.
First Checks
- Call
channel_catalogto see supported channels. - Call
channel_manifestfor the exact selected channel. - Call
channel_setup_requirementsto read required env vars, fields, direct-send support, and policy defaults. - Call
channel_doctorbefore sending or declaring setup complete. - Call
channel_integration_smokefor a non-sending readiness report covering setup, prepared outbox, dry-run send wiring, and listener state. - Call
channel_listener_statusbefore declaring the agent is listening.
Setup State
Use channel_setup_save for:
enabledconversation_defaultsallowlistgroup_allowlistsecret_refssuch as{"bot_token":"SLACK_BOT_TOKEN"}- notes
Do not put raw tokens, app secrets, OAuth refresh tokens, phone auth state, QR session files, or private keys in setup JSON.
Testing A Channel
For a non-destructive smoke:
- Run
channel_integration_smokefor the selected channel. - Prepare a message with
channel_message_preparewhen you need to inspect the exact outbound envelope. - Prepare reactions, file shares, thread replies, pins, typing indicators, or read receipts with
channel_action_prepare. - Inspect
channel_outbox. - For inbound harness smoke, pass an inbound channel message with explicit
requires_response:true. - For webhook smoke, use
channel_webhook_ingestwith a structured provider payload. - For Telegram listener smoke, use
channel_listener_tickafter enabling the channel and configuringTELEGRAM_BOT_TOKEN. - Confirm a prepared reply exists only for non-ambient request messages.
- For external send smoke, use
channel_message_sendonly with approval and a test recipient or room.
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 · 104 lines · 21 tokens per session scan A fe50f0b8a409
channel-operations is a skill published in the GitHub repository CodeInfinity1/Stram (10 stars, last pushed 23d ago), licensed MIT. It adds 21 tokens to every session and 1,062 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
golden-rss
Use when testing the rss golden build.
omh-buzz
This is a Hermes-native buzz workflow skill.
redteam-api-detail-pack
Domain routing and boundary guidance for authorized API security testing, including BOLA/IDOR, authentication bypass, mass assignment, missing rate limits, and GraphQL issues. Use when a task belongs to the API testing domain and needs scope, evidence, pivot, or exit criteria.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
manage-schemas
Creates, views, edits, deletes, and validates note schemas for the MCP Task Orchestrator in .taskorchestrator/config.yaml — the templates that define which notes agents must fill at each workflow phase. Also recommends schema designs from a library of workflow patterns (autonomous coding loops, spec-driven teams…