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 Knuckles-Team/mattermost-mcp --skill mattermost-team-administrationgit clone --depth 1 https://github.com/Knuckles-Team/mattermost-mcpWrote 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/knuckles-team/mattermost-mcp/mattermost-team-administration)<a href="https://agentmods.dev/skills/knuckles-team/mattermost-mcp/mattermost-team-administration"><img src="https://agentmods.dev/badge/skills/knuckles-team/mattermost-mcp/mattermost-team-administration/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/knuckles-team/mattermost-mcp/mattermost-team-administration"><img src="https://agentmods.dev/badge/skills/knuckles-team/mattermost-mcp/mattermost-team-administration.svg" alt="Reviewed on agentmods" width="80" 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.00112 | $0.01092 |
| Opus 5 | $0.00056 | $0.00546 |
| Sonnet 5 | $0.00022 | $0.00218 |
| Haiku 4.5 | $0.00011 | $0.00109 |
Grade A, and why
mattermost-team-administration 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 10d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mattermost Team Administration
Domain-typed access to Mattermost teams, channels, and their membership. Prefer these tools over raw HTTP — they carry the team/channel field conventions and return team/channel-shaped records.
When to use
- List or create teams; look a team up by name; read team stats and members.
- List, create, rename, archive, or restore channels within a team.
- Set channel privacy (public
O↔ privateP). - Add or remove team / channel members.
When NOT to use
- Read or post messages / threads / files →
mattermost-channel-messaging. - Mirror teams/channels/users into the knowledge graph →
mattermost-kg-ingestion. - Server-wide system/compliance/plugins config → use the corresponding condensed
tool (
mattermost_mcp_system,mattermost_mcp_compliance, …) directly.
Prerequisites & environment
Connect via the mcp-client skill against the mattermost-mcp MCP server.
| Variable | Required | Notes |
|---|---|---|
MATTERMOST_URL |
✅ | Server base URL (alias MATTERMOST_MCP_BASE_URL) |
MATTERMOST_TOKEN |
✅* | Personal-access / bot token (needs admin scope for create/delete) |
MATTERMOST_MCP_USERNAME / MATTERMOST_MCP_PASSWORD |
✅* | Login fallback if no token |
MATTERMOST_MCP_SSL_VERIFY |
optional | TLS verification toggle |
*Provide either a token or username+password. MCP_TOOL_MODE selects the condensed
vs. verbose surface.
Tools & actions
Prefer the condensed tools; each takes action + a params_json JSON string.
| Condensed tool | Key actions |
|---|---|
mattermost_mcp_teams |
get_all_teams, create_team, get_team, get_team_by_name, get_team_members, add_team_member, remove_team_member, get_team_stats |
mattermost_mcp_channels |
get_public_channels_for_team, create_channel, get_channel, get_channel_by_name, patch_channel, update_channel_privacy, delete_channel, restore_channel, add_channel_member, remove_user_from_channel, get_channel_members |
What ships with it
1 file 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.
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.
- 10d ago First seen · 94 lines · 112 tokens per session scan A b59a6ebfccd5
mattermost-team-administration is a skill published in the GitHub repository Knuckles-Team/mattermost-mcp (0 stars, last pushed 13d ago), licensed MIT. It adds 112 tokens to every session and 1,092 once invoked, about $0.0006 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
slackdump
Collect the Slack conversation data from Slackdump Archive format.
slackdump-sqlite3
Guidance for querying a Slackdump SQLite3 database directly via the sqlite3 CLI.
curate-collection
Build and maintain a library collection through acquisitions, weeding (deaccessioning), collection assessment, reader advisory, and interlibrary loan coordination. Covers selection criteria, collection development policies, the CREW/MUSTIE method for weeding, usage analysis, and responsive collection management. Use…
design-on-call-rotation
Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or…
design-training-program
Design a GxP training programme covering training needs analysis by role, curriculum design (regulatory awareness, system-specific, data integrity), competency assessment criteria, training record retention, and retraining triggers for SOP revisions and incidents. Use when a new validated system requires user training…
slackdump-source
Explains the different Slackdump sources structure.