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 CodeInfinity1/Stram --skill channel-gateway-operationsgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/channel-gateway-operations)<a href="https://agentmods.dev/skills/codeinfinity1/stram/channel-gateway-operations"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/channel-gateway-operations/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/codeinfinity1/stram/channel-gateway-operations"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/channel-gateway-operations.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.00046 | $0.00724 |
| Opus 5.5 | $0.00018 | $0.00290 |
| Sonnet 5.5 | $0.00009 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
channel-gateway-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 1mo 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.
Channel Gateway Operations
Purpose
Operate channels as native Stram transport surfaces. This skill turns native Gateway patterns into Stram-owned catalog, setup, policy, outbox, and interaction-harness workflows.
When To Use
Use when the task involves multiple channels, channel onboarding, gateway manifests, inbound event routing, outbound delivery, quiet room context, bot-loop suppression, or deciding whether a channel can send directly.
Inputs And Evidence
channel_id,conversation_id, conversation type, sender ID, message ID, mention state, and bot-authored flags.- Channel catalog or manifest output.
- Setup status, missing environment variables, allowlists, and group policy.
- Outbox item, send result, or inbound stimulus record.
Tool Map
channel_catalogchannel_manifestchannel_setup_requirementschannel_setup_statuschannel_doctorchannel_integration_smokechannel_listener_statuschannel_webhook_ingestchannel_action_preparechannel_message_preparechannel_message_sendchannel_outboxactivity_ingestcognitive_interaction_review
Workflow
- Start with
channel_catalogorchannel_manifestfor the exact channel. - Inspect setup requirements and status before assuming direct send support.
- Run
channel_integration_smokefor non-sending readiness evidence. - Preserve structured metadata for inbound events; do not infer routing from message text alone.
- Apply channel policy: allowlist, pairing, mention, ambient room, bot-loop, and approval boundaries.
- Route accepted inbound messages as channel stimuli into the normal interaction harness.
- For outbound work, prepare an outbox envelope first unless a direct send is explicitly approved and configured.
- Report the exact delivery status: prepared, blocked, failed, dry run, or sent.
Native Implementation Boundaries
- Use only Stram Gateway tools and owned adapters.
- Do not import external reference Gateway code, external skill catalog plugins, or external channel packages as the skill implementation.
- If a channel is cataloged but direct runtime support is missing, say that clearly and use prepared outbox or setup planning.
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.
- 1mo ago First seen · 82 lines · 46 tokens per session scan A 782eeb095fde
channel-gateway-operations is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 724 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
lighting-report-extract
Check reported lighting quantities and results in supplied simulation PDFs without adding repeated calculation surfaces. Use for scoped luminaire inventories and illuminance results; not simulation or compliance.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
container-debugging
Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.
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.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…