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 internal-comms-writinggit 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/internal-comms-writing)<a href="https://agentmods.dev/skills/codeinfinity1/stram/internal-comms-writing"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/internal-comms-writing/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/internal-comms-writing"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/internal-comms-writing.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.00033 | $0.00537 |
| Opus 5.5 | $0.00013 | $0.00215 |
| Sonnet 5.5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
internal-comms-writing 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Internal Comms Writing
Purpose
Help the user communicate inside teams with clarity, context, and appropriate tone. This skill adapts internal-communications writing patterns into Stram-native drafting, notes, channel preparation, and approval workflows.
When To Use
Use for team updates, exec summaries, incident notes, rollout announcements, FAQ drafts, policy notes, newsletters, planning messages, and post-meeting communications.
Inputs And Evidence
- Audience, channel, purpose, deadline, desired tone, and length.
- Source evidence such as meeting notes, task status, logs, docs, or user bullets.
- Sensitive details that must be included, excluded, or anonymized.
- Delivery channel setup and approval state.
Tool Map
writing_draft_createwriting_draft_inspectread_filewrite_notememory_writechannel_message_preparevoice_response_preparecognitive_interaction_reviewmessage-approval-policy
Workflow
- Identify audience and purpose before drafting.
- Separate verified facts from assumptions and open questions.
- Choose a format: short update, FAQ, incident note, announcement, newsletter, or decision memo.
- Draft in a concise, direct style with clear next actions.
- Save a durable unsent draft with
writing_draft_createwhen persistence is useful. - Prepare a channel message or note when delivery/persistence is requested.
- Use approval gates before external-visible or team-visible posting.
Native Implementation Boundaries
- Use Stram document, note, channel, and cognition tools.
- Do not import Anthropic or external reference communication skill code as implementation.
- Use upstream writing examples only as reference inspiration.
Safety And Approval
- Do not overstate certainty, blame individuals, or disclose private data.
- Incident and executive comms should preserve uncertainty and known scope.
- User approval is required before posting.
Verification
- Confirm each claim maps to evidence or is clearly framed as a draft assumption.
- Confirm audience and channel match the user's request.
- Confirm a prepared message is not described as sent.
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 · 73 lines · 33 tokens per session scan A 5202ab3e85db
internal-comms-writing is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 537 once invoked, about $0.0001 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…