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-adaptive-cardsgit 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-adaptive-cards)<a href="https://agentmods.dev/skills/ccheney/robust-skills/teams-adaptive-cards"><img src="https://agentmods.dev/badge/skills/ccheney/robust-skills/teams-adaptive-cards/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-adaptive-cards"><img src="https://agentmods.dev/badge/skills/ccheney/robust-skills/teams-adaptive-cards.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.00142 | $0.03036 |
| Opus 5 | $0.00071 | $0.01518 |
| Sonnet 5 | $0.00028 | $0.00607 |
| Haiku 4.5 | $0.00014 | $0.00304 |
Grade A, and why
teams-adaptive-cards 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 12d 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Teams Adaptive Cards
Adaptive Cards are the primary rich-message surface for Microsoft Teams. Always choose the transport first, because the same card JSON is wrapped differently for bots, Workflows webhooks, and Microsoft Graph — most broken Teams cards are wrapper mistakes, not card mistakes.
Quick Decision Trees
"Should I use a card?"
Response type?
|-- Short conversational reply, <3 lines -> text only; use $teams-message-formatting
|-- Status notification with facts/actions -> Adaptive Card
|-- Approval, form, or data collection -> Adaptive Card through bot/Universal Actions
|-- Search result or message extension response -> Adaptive Card
|-- Service alert to a channel -> Workflows webhook or notification bot card
|-- Delegated Graph message with attachment -> Graph chatMessage card wrapper
`-- Legacy connector/MessageCard payload -> migrate to Workflows + Adaptive Card
(O365 connectors stopped working May 2026)
"Which transport wrapper?"
Delivery path?
|-- Bot Framework / Teams SDK
| `-- Activity `attachments[]` with contentType `application/vnd.microsoft.card.adaptive`
|-- Workflows (Power Automate) webhook
| `-- Top-level `{ "type": "message", "attachments": [...] }`
| (same wrapper the retired Incoming Webhook connectors used)
|-- Microsoft Graph chatMessage
| `-- Body `<attachment id="..."></attachment>` plus matching `attachments[]`
| with the card as a JSON *string* in attachment content
|-- Message extension result
| `-- Attachment with Adaptive Card content and preview as required by extension type
`-- Outlook + Teams universal scenario
`-- Use Universal Actions (`Action.Execute`) with bot backend
"Which card version?"
Need maximum Teams mobile compatibility?
|-- Yes -> use version "1.2"
`-- No
|-- Need Action.Execute / refresh / Universal Actions -> version "1.4"+, bot-backed
|-- Need Table / CodeBlock / charts / Icon / targetWidth -> version "1.5"
`-- No special features -> version "1.2"
What ships with it
9 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.
- agents/openai.yaml 259 B
- references/ACTIONS.md 7.1 KB
- references/CHEATSHEET.md 6.3 KB
- references/ELEMENTS.md 9.3 KB
- references/GRAPH-ATTACHMENTS.md 4.7 KB
- references/RESPONSIVE-DESIGN.md 5.3 KB
- references/SURFACES.md 6.2 KB
- references/WEBHOOKS-WORKFLOWS.md 6.1 KB
- scripts/check-teams-card.mjs 18 KB runs code
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.
- 12d ago First seen · 243 lines · 142 tokens per session scan A b99720fdc67e
teams-adaptive-cards is a skill published in the GitHub repository ccheney/robust-skills (59 stars, last pushed 16d ago), licensed MIT. It adds 142 tokens to every session and 3,036 once invoked, about $0.0007 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
principle-product-design
UX and product design principles — Nielsen's 10 usability heuristics, visual hierarchy, interaction design patterns, design-system compliance, and responsive layout. Accessibility/WCAG conformance is delegated to swe-workbench:principle-accessibility. Auto-load when reviewing UX, evaluating usability, assessing visual…
principle-accessibility
Accessibility (a11y) principles — WCAG 2.2 AA conformance, semantic HTML, keyboard navigation, focus management, focus traps, color contrast, alt text, screen reader compatibility, reduced motion. Auto-load when reviewing frontend or UI code, evaluating ARIA usage, auditing color contrast, building modals or dialogs…
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
ima-dai-sdk
Integrates the Google Interactive Media Ads (IMA) Dynamic Ad Insertion (DAI) SDK into websites, web apps, mobile apps, or TV apps. Use when: - A video player needs to load and play HLS or DASH streams in web apps, Android apps, iOS apps, tvOS apps, Cast (CAF) receivers, or Roku channels. - The app needs to make use of…
migrate-xml-views-to-jetpack-compose
Provides a structured workflow for migrating an Android XML View to Jetpack Compose. This skill details the step-by-step process, from planning and dependency setup, to theming and layout migration, validation and XML cleanup. Use this skill when you need to migrate an XML View to Jetpack Compose in an Android…
gpt-image-2
A skill for generating or editing images with GPT Image 2 across local, host-provided, or advisory setups.