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/webchat-operationsnpx skills add CodeInfinity1/Stram --skill webchat-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.00033 | $0.00529 |
| Opus 5 | $0.00016 | $0.00264 |
| Sonnet 5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
webchat-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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WebChat Operations
Purpose
Treat WebChat as the local/browser-facing user interface channel. This skill supports WebChat setup, event routing, user-visible replies, and debugging without depending on external reference WebChat code.
When To Use
Use when building or diagnosing the browser chat UI, WebSocket events, local Gateway messages, WebChat onboarding, or user-facing channel previews.
Inputs And Evidence
- WebChat session ID, user ID, conversation ID, or browser runtime metadata.
- Channel manifest for
webchat. - Local UI/server status.
- Outbox entries or interaction harness run IDs.
Tool Map
channel_manifestchannel_setup_statuschannel_message_preparechannel_outboxactivity_ingestcognitive_interaction_reviewbrowser_live_openbrowser_live_observe
Workflow
- Read the WebChat manifest and determine whether the local UI/runtime is active.
- Route inbound WebChat text as structured channel stimuli with session metadata.
- Use the same cognitive decision path as voice and other channels.
- Prepare outbound messages when the runtime consumes outbox envelopes.
- If testing the UI, use live browser tools to observe the local WebChat page.
- Keep WebChat delivery claims tied to runtime acknowledgement, not only message preparation.
Native Implementation Boundaries
- Implement WebChat runtime and WebSocket behavior in Stram-owned code.
- Do not import external reference WebChat UI or Gateway implementation.
- If only the outbox contract exists, say the UI/runtime handoff is pending.
Safety And Approval
- WebChat may expose local files, logs, and tool results; redact secrets before display.
- Keep external channel sends separate from WebChat local replies.
- Do not assume a WebChat user is authenticated unless the runtime supplies identity evidence.
Verification
- Confirm manifest and setup status.
- Confirm browser UI state when testing local WebChat.
- Confirm outbox or runtime acknowledgement for any visible reply.
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 · 72 lines · 33 tokens per session scan A 651ed8c1e07b
webchat-operations is a skill published in the GitHub repository CodeInfinity1/Stram (10 stars, last pushed 22d ago), licensed MIT. It adds 33 tokens to every session and 529 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
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.