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/gtapps/msteams-channel/releasenpx skills add gtapps/msteams-channel --skill releasegit clone --depth 1 https://github.com/gtapps/msteams-channelWrote 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/gtapps/msteams-channel/release)<a href="https://agentmods.dev/skills/gtapps/msteams-channel/release"><img src="https://agentmods.dev/badge/skills/gtapps/msteams-channel/release.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.00089 | $0.03773 |
| Opus 5 | $0.00044 | $0.01886 |
| Sonnet 5 | $0.00018 | $0.00755 |
| Haiku 4.5 | $0.00009 | $0.00377 |
Grade A, and why
release 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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Cut a release of the msteams channel plugin. This repo is its own marketplace:
the plugin lives at the repo root and .claude-plugin/marketplace.json points at
./, so users install it straight from GitHub with
/plugin marketplace add gtapps/msteams-channel. There is no registry and no
build artifact — the git tag plus the pushed commit are the release, and a
user's /plugin update pulls whatever main says.
That has one consequence worth internalizing before you start: an unreleased
commit on main is already live for anyone who runs /plugin marketplace update.
The tag is a marker for humans and for version-gated updates, not a gate on
distribution. So main must never carry a state you would not ship.
Usage
/release — infer the bump level from the changes since the last tag.
/release patch|minor|major — force a bump level.
/release 0.2.0 — force an exact version.
The four version locations
Every release sets all four to the same X.Y.Z. claude plugin tag only
checks the first and the third, so the other two are on you.
| Location | How to read it |
|---|---|
.claude-plugin/plugin.json |
jq -r '.version' |
package.json |
jq -r '.version' |
.claude-plugin/marketplace.json |
jq -r '.plugins[] | select(.name=="msteams") | .version' |
server.ts |
the { name: 'msteams', version: 'X.Y.Z' } literal in the Server constructor (~line 100) |
The server.ts literal is what a client sees in the MCP initialize response,
so a stale one misreports the running build to anyone debugging a live session.
Edit it with the Edit tool, never a blind sed — the file contains other
version strings.
Steps
1. Pre-release validation
Run all of these first. Abort on any failure — a bad tag on a repo that is the
distribution channel is live for users the moment it lands on main.
bun install --frozen-lockfile # lockfile must be current, not "fixable"
bun run typecheck # tsc --noEmit
bun test # 249+ tests, ~11s, no tenant or network
claude plugin validate . # must print Validation passed (warnings ok)
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 · 341 lines · 89 tokens per session scan A 02c31dfab88f
release is a skill published in the GitHub repository gtapps/msteams-channel (2 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 3,773 once invoked, about $0.0004 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
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
release
Prepare, cut, and verify a warren release — tracker audits, version bump, CHANGELOG curation, ROADMAP update, push, then watch the pipeline through to published artifacts.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
ops-release
OPS on-demand: This skill should be used when the user asks to "release the plugin", "publish ops…
bump-version
Bump package and plugin version in sync. Updates package.json, .claude-plugin/plugin.json, and install-state manifest to the same version. Use when: user says 'bump version', 'update version', '更新版本', '版本 +1', or /bump-version.