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/breadchaincoop/labor.fun/add-teamsnpx skills add BreadchainCoop/labor.fun --skill add-teamsgit clone --depth 1 https://github.com/BreadchainCoop/labor.funWrote 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/breadchaincoop/labor.fun/add-teams)<a href="https://agentmods.dev/skills/breadchaincoop/labor.fun/add-teams"><img src="https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/add-teams.svg" alt="Measured on agentmods" height="20"></a>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.00048 | $0.01326 |
| Opus 5 | $0.00024 | $0.00663 |
| Sonnet 5 | $0.00010 | $0.00265 |
| Haiku 4.5 | $0.00005 | $0.00133 |
Grade A, and why
add-teams 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 5d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Microsoft Teams Channel
The Teams channel is built in (src/channels/teams.ts, via the Bot Framework).
Unlike branch-merged channels there is no code to merge — it stays inert
until TEAMS_ENABLED=true and the Azure Bot credentials are set. This skill
walks the operator through the Azure setup and configuration.
Phase 1: Pre-flight
Check state
- Confirm
src/channels/teams.tsexists (it should — it's in main). If not, the install predates the Teams channel; run/update-nanoclawfirst. - Teams delivery is HTTP push from the Bot Framework, so the messaging endpoint must be reachable at a public HTTPS URL (a domain + TLS, or a tunnel for testing). Unlike Slack Socket Mode, there is no no-public-URL mode.
Ask the user
- The public HTTPS base URL that will front the bot (e.g.
https://bot.acme.com). - Whether they can create an Azure Bot resource (needs an Azure subscription + permission to register an Entra ID / Azure AD app).
Phase 2: Azure Bot registration
Guide the user through the Azure portal (portal.azure.com):
- Create an Azure Bot resource ("Azure Bot" in the Marketplace).
- App type: Multi-tenant (simplest) or Single-tenant (then capture the tenant id). Let Azure create a new Microsoft App ID.
- From the bot's Configuration blade, copy the Microsoft App ID →
TEAMS_APP_ID. If single-tenant, copy the App Tenant ID →TEAMS_APP_TENANT_ID(leave empty for multi-tenant). - Manage the app → Certificates & secrets → New client secret →
copy the secret Value (not the id) →
TEAMS_APP_PASSWORD. It is shown once; store it in the vault /.envimmediately. - Set the bot's Messaging endpoint to
https://<your-public-host>/api/messages. The channel accepts the Bot Framework activity on any path (POST), and answersGETas a health probe;/api/messagesis just the Bot Framework convention. The port is internal — front it with your reverse proxy / TLS terminator. - Under Channels, add the Microsoft Teams channel.
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.
- 5d ago First seen · 115 lines · 48 tokens per session scan A 8d1e1047a471
add-teams is a skill published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 1,326 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…