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/daocoding/claude-teams/configurenpx skills add daocoding/claude-teams --skill configuregit clone --depth 1 https://github.com/daocoding/claude-teamsWhat 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.00038 | $0.00412 |
| Opus 5 | $0.00019 | $0.00206 |
| Sonnet 5 | $0.00008 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
configure 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.
What it actually says
/teams:configure
Configure the Teams channel bot credentials.
Usage
/teams:configure— show current status/teams:configure <APP_ID> <APP_PASSWORD> <TENANT_ID>— save credentials/teams:configure clear— remove saved credentials
What it does
Writes credentials to ~/.claude/channels/teams/.env with mode 0600:
MICROSOFT_APP_ID=<APP_ID>
MICROSOFT_APP_PASSWORD=<APP_PASSWORD>
MICROSOFT_TENANT_ID=<TENANT_ID>
Create the directory if it doesn't exist: mkdir -p ~/.claude/channels/teams
After configuring
- Restart Claude Code or run
/reload-pluginsfor changes to take effect - Launch with the channel flag:
claude --channels plugin:teams-channel - Expose the webhook endpoint (port 3980 by default) via a public HTTPS URL
- Register the webhook URL in your Azure Bot registration under "Messaging endpoint"
Status display (no arguments)
When run without arguments, read ~/.claude/channels/teams/.env and ~/.claude/channels/teams/access.json and display:
- Whether credentials are saved (show App ID, mask password)
- Current DM policy
- Number of allowed conversations
- Number of pending pairings
- Next steps if anything is missing
Security note
pairing mode is a temporary bootstrap — use it to capture conversation IDs, then switch to allowlist mode via /teams:access policy allowlist.
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 · 53 lines · 38 tokens per session scan A 6acf1cd5b23f
configure is a skill published in the GitHub repository daocoding/claude-teams (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 412 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.