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 signal-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/signal-operations)<a href="https://agentmods.dev/skills/codeinfinity1/stram/signal-operations"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/signal-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/signal-operations"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/signal-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.00032 | $0.00501 |
| Opus 5.5 | $0.00013 | $0.00200 |
| Sonnet 5.5 | $0.00006 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
signal-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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Signal Operations
Purpose
Represent Signal as a privacy-focused native channel contract. Stram catalogs Signal and can prepare audited outbox messages; actual account delivery requires a trusted local signal-cli bridge.
When To Use
Use when the user asks about Signal onboarding, Signal private messages, group Signal chats, local bridge requirements, or privacy-preserving channel choices.
Inputs And Evidence
- Phone number, Signal account reference, or group ID.
channel_manifestforsignal.- signal-cli binary availability from
channel_doctor. - Allowlist and pairing state.
- Prepared outbox envelope.
Tool Map
channel_manifestchannel_setup_requirementschannel_setup_statuschannel_doctorchannel_message_preparechannel_outboxmessage-approval-policy
Workflow
- Read the
signalmanifest and setup requirements. - Run
channel_doctorto check whethersignal-cliis available. - Confirm the exact recipient or group ID and allowlist status.
- Prepare outbound messages through
channel_message_prepare. - If a trusted local bridge is not active, report that delivery is prepared but not sent.
- Keep Signal state and account pairing inside the trusted bridge boundary.
Native Implementation Boundaries
- Stram must own any signal-cli bridge adapter it uses.
- Do not install or call external reference Signal plugins as implementation.
- Do not claim direct delivery until the native bridge returns a sent status.
Safety And Approval
- Signal messages can be sensitive; never auto-send.
- Do not store Signal private keys or pairing artifacts in skill files or setup JSON.
- Use exact recipients, exact text, and explicit user approval.
Verification
channel_doctorshould reveal binary/setup gaps.channel_outboxproves prepared envelopes.- Direct send support remains blocked unless a native bridge is implemented and configured.
Failure Modes
- Confusing prepared outbox with encrypted delivery.
- Sending to a phone number that was not allowlisted.
- Leaking Signal account metadata into unrelated memory records.
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 · 72 lines · 32 tokens per session scan A b422e813e3d9
signal-operations is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 501 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…