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 ccheney/robust-skills --skill teams-message-formattinggit clone --depth 1 https://github.com/ccheney/robust-skillsWrote 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/ccheney/robust-skills/teams-message-formatting)<a href="https://agentmods.dev/skills/ccheney/robust-skills/teams-message-formatting"><img src="https://agentmods.dev/badge/skills/ccheney/robust-skills/teams-message-formatting/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/ccheney/robust-skills/teams-message-formatting"><img src="https://agentmods.dev/badge/skills/ccheney/robust-skills/teams-message-formatting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00168 | $0.02442 |
| Opus 5 | $0.00084 | $0.01221 |
| Sonnet 5 | $0.00034 | $0.00488 |
| Haiku 4.5 | $0.00017 | $0.00244 |
Grade A, and why
teams-message-formatting 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 9d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Teams Message Formatting
Microsoft Teams has several incompatible text systems. Pick the surface first, then write the text for that surface — most rendering bugs come from using one surface's syntax on another.
CRITICAL: Four Markup Systems
| System | Used In | Bold | Link | Mention |
|---|---|---|---|---|
Bot text markdown |
Bot Framework/Teams SDK activity text (default) |
**bold** |
[text](url) |
<at>Name</at> plus activity entities |
Bot text xml |
Bot activity textFormat: "xml" and hero/thumbnail card text |
<strong>bold</strong> |
<a href="url">text</a> |
<at>Name</at> plus activity entities |
| Adaptive Card Markdown | TextBlock.text, Fact.title, Fact.value |
**bold** |
[text](url) |
<at>Name</at> plus root msteams.entities |
Graph chatMessage HTML |
Microsoft Graph chatMessage.body.contentType: "html" |
<strong>bold</strong> |
<a href="url">text</a> |
<at id="0">Name</at> plus mentions array |
Do not mix them. Slack mrkdwn (*bold*, <url|text>) is wrong everywhere in Teams. Full standard Markdown is also wrong in Adaptive Cards: headings, tables, images, preformatted text, and blockquotes are not supported in TextBlock.
Quick Decision Tree
What are you formatting?
|-- Bot reply or proactive bot message
| |-- Simple text -> textFormat "markdown" (or SDK default)
| |-- User/tag mention -> <at>...</at> plus activity entities
| `-- Rich UI, inputs, buttons -> Adaptive Card ($teams-adaptive-cards)
|-- Adaptive Card text
| |-- TextBlock / FactSet -> limited Adaptive Card Markdown only
| |-- Heading -> TextBlock size/weight/style, never `#`
| |-- Table -> Table element, never Markdown table
| `-- Code -> CodeBlock element, never backticks
|-- Microsoft Graph chatMessage (delegated send)
| |-- Plain text -> body contentType "text"
| |-- Formatting, mentions, emoji, code -> body contentType "html"
| `-- Adaptive Card -> <attachment id> placeholder + attachments
|-- Service-to-channel webhook
| |-- Anything new -> Workflows webhook + Adaptive Card wrapper
| `-- Legacy webhook.office.com URL -> retired May 2026; migrate to Workflows
`-- Hero/thumbnail card -> XML/HTML subset in `text` only; no Markdown,
no formatting in title/subtitle
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 162 lines · 168 tokens per session scan A bc32b4cd27e0
teams-message-formatting is a skill published in the GitHub repository ccheney/robust-skills (57 stars, last pushed 13d ago), licensed MIT. It adds 168 tokens to every session and 2,442 once invoked, about $0.0008 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-30.
Other skills, from other repositories
clean-code
Use when writing, editing, reviewing, testing, or refactoring code in any language or framework; when creating files or deciding where code belongs; when designing or changing module boundaries, layers, and dependencies; when starting a new project; or when auditing or cleaning up an existing one. Covers naming…
workflow-branch-sync
Sync the current branch with the default branch via rimba or git, then resolve conflicts file by file with a per-hunk rationale and a keep-mine / keep-main / manual recommendation before staging. Push only happens after explicit confirmation — never automatic.
workflow-pr-review
Use when reviewing a remote GitHub PR — a first-pass peer review, or a followup re-check after the owner has addressed feedback. Fetches into an ephemeral worktree, runs the reviewer agent against the updated diff with a Review Decision footer instruction, deduplicates findings against existing review threads (±5-line…
workflow-address-feedback
Use when a PR owner wants to address review feedback — fetches outstanding threads and general comments, presents a per-item triage (ADDRESSED / CLARIFIED / DEFERRED), applies fixes via the Edit tool, commits via workflow-commit-and-pr, resolves review threads via GraphQL resolveReviewThread (those without a thread…
workflow-commit-and-pr
Use when the user wants to commit staged changes or create a PR — enforces trigger-phrase discipline (preview vs commit vs ship), the [type] commit format, branch-naming check, draft-vs-ready PR prompt, and PR template detection. Pre-merge counterpart to workflow-cleanup-merged.
workflow-development
Development workflow — full lifecycle from Branch → Implement → Verify → Review → Deliver. Activated by /swe-workbench:implement, /swe-workbench:design, /swe-workbench:refactor, /swe-workbench:debug, /swe-workbench:test, /swe-workbench:architect, /swe-workbench:migrate, and /swe-workbench:document when the plan being…