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/teams-operationsnpx skills add CodeInfinity1/Stram --skill teams-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.00035 | $0.00594 |
| Opus 5 | $0.00017 | $0.00297 |
| Sonnet 5 | $0.00007 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
teams-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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Teams Operations
Purpose
Use Microsoft Teams as an enterprise communication surface without depending on external reference or external reference runtime code. Stram currently supports Teams catalog/setup and webhook text sends through native channel adapters, with full Bot Framework behavior represented as a trusted-runtime contract.
When To Use
Use for Teams channel onboarding, Teams webhook sends, meeting follow-ups, Teams-style group messages, enterprise status updates, or diagnosing Teams Gateway readiness.
Inputs And Evidence
- Teams channel or conversation ID.
TEAMS_WEBHOOK_URLreadiness or Bot Framework credential references.- Meeting summary, follow-up message, or status update draft.
- Channel manifest and doctor output.
Tool Map
channel_manifestchannel_setup_requirementschannel_setup_statuschannel_doctorchannel_message_preparechannel_message_sendmeeting-follow-upmessage-approval-policy
Workflow
- Read
channel_manifestformsteams. - Run
channel_setup_requirementsand confirm whether simple webhook or full bot behavior is intended. - Use
channel_doctorto checkTEAMS_WEBHOOK_URLfor native direct text send readiness. - Draft meeting follow-ups or status updates with clear recipients and channel context.
- Prepare messages first with
channel_message_prepare. - Use
channel_message_sendonly after approval and only when the webhook adapter is configured. - Mark Bot Framework inbound/listener needs as implementation gaps unless a native trusted runtime is present.
Native Implementation Boundaries
- Use Stram's
msteamscatalog entry and native webhook sender. - Do not import external reference Teams plugins or external reference Teams pipeline code.
- Use meeting skills for summarization/follow-up logic, not upstream Teams scripts.
Safety And Approval
- Teams rooms are external-visible workspaces; always require approval before sending.
- Keep confidential meeting notes out of broad channels unless the user confirms audience.
- Treat Teams webhook URLs as secrets.
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 · 73 lines · 35 tokens per session scan A decd35402436
teams-operations is a skill published in the GitHub repository CodeInfinity1/Stram (10 stars, last pushed 22d ago), licensed MIT. It adds 35 tokens to every session and 594 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、自动化测试、运行态驱动、签名恢复、抓包分析.
mnemon
Persistent memory for MiniMax Code. Recall durable context, store important facts and decisions, and link related memories with the mnemon CLI.