Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sliamh11/Deusnpx agentmods add skills/sliamh11/deus/add-msft-teamsWrote 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/sliamh11/deus/add-msft-teams)<a href="https://agentmods.dev/skills/sliamh11/deus/add-msft-teams"><img src="https://agentmods.dev/badge/skills/sliamh11/deus/add-msft-teams/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/sliamh11/deus/add-msft-teams"><img src="https://agentmods.dev/badge/skills/sliamh11/deus/add-msft-teams.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Privilege Escalation · line 77 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium MCP Rug Pull · line 97 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 102 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 108 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 116 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Privilege Escalation · line 162 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00040 | $0.01941 |
| Opus 5 | $0.00020 | $0.00971 |
| Sonnet 5 | $0.00008 | $0.00388 |
| Haiku 4.5 | $0.00004 | $0.00194 |
Grade B, and why
add-msft-teams scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo systemctl restart deus How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Microsoft Teams Channel
Status: Available in-repo as
packages/mcp-teams/(@deus-ai/teams-mcp). The published npm package is not out yet, so the channel factory falls back to the in-repo build atpackages/mcp-teams/dist/index.js— you build it locally (below).
Microsoft Teams is the chat-channel analog of Slack: a bot identity receives
messages and posts replies. Unlike Slack's Socket Mode, the Teams bot uses the
Azure Bot Service (Bot Framework), which delivers activities to a public
HTTPS messaging endpoint. The channel runs its own HTTP server on TEAMS_PORT
(default 3978) serving /api/messages; you must expose that port via a
dedicated public tunnel (see below) — Deus's existing ingress tunnel forwards
only the gateway port and does not cover TEAMS_PORT.
Phase 1: Setup
Register the Azure app + bot (if needed)
If the user doesn't have an Azure Bot, walk them through it. Quick summary of what's needed:
-
In the Azure Portal → Microsoft Entra ID → App registrations → New registration. Copy the Application (client) ID and Directory (tenant) ID.
-
Certificates & secrets → New client secret → copy the secret value (shown once).
-
Start a dedicated tunnel to the Teams port (any HTTPS tunnel works):
ngrok http 3978 # → forwards a public https URL to http://localhost:3978 -
Create an Azure Bot resource (Azure Bot Service). Link it to the app registration above (the Microsoft App ID). Set the messaging endpoint to your tunnel's URL:
https://<your-tunnel-domain>/api/messages. -
On the bot resource → Channels → enable the Microsoft Teams channel.
-
Create a Teams app (Developer Portal for Teams / manifest) that references the bot's App ID, then install it to a team or chat.
The messaging endpoint must be a public HTTPS URL reaching
TEAMS_PORT. A local-only endpoint (or the gateway tunnel) will not receive Bot Framework activities — use a dedicated tunnel to port 3978.
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 · 194 lines · 40 tokens per session scan B 8465dd5e9ac6
add-msft-teams is a skill published in the GitHub repository sliamh11/Deus (51 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 1,941 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
memcord
Privacy-first, self-hosted chat memory for OpenClaw — save and recall conversation history across sessions without any cloud dependency.
roadmap-build
Build or repair a roadmap that agents can actually execute, not just read. Produces a single validated YAML source of truth, generated views, definitions of done with evidence kinds, a task pool linked on two axes, an idea intake queue, and three standing checks that keep it honest. Use when asked to "build a…
Research for Datacore
Automated research — source processing, podcast generation, and knowledge extraction.
GTD for Datacore
Getting Things Done — task capture, inbox processing, and org-mode management.
Outbox for Datacore
Content routing — archive to server, search archived content.
research-status
Check research queue counts, recent podcasts, knowledge base growth, and Readwise items.