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 olgasafonova/mediawiki-mcp-server --skill wiki-publishgit clone --depth 1 https://github.com/olgasafonova/mediawiki-mcp-serverWrote 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/olgasafonova/mediawiki-mcp-server/wiki-publish)<a href="https://agentmods.dev/skills/olgasafonova/mediawiki-mcp-server/wiki-publish"><img src="https://agentmods.dev/badge/skills/olgasafonova/mediawiki-mcp-server/wiki-publish/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/olgasafonova/mediawiki-mcp-server/wiki-publish"><img src="https://agentmods.dev/badge/skills/olgasafonova/mediawiki-mcp-server/wiki-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00057 | $0.00802 |
| Opus 5 | $0.00028 | $0.00401 |
| Sonnet 5 | $0.00011 | $0.00160 |
| Haiku 4.5 | $0.00006 | $0.00080 |
Grade A, and why
wiki-publish 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 12d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wiki-publish
Publishes a markdown file to a MediaWiki wiki by shelling out to the wiki CLI. The plugin never re-implements wiki logic; the CLI is the contract.
Prerequisites
The wiki CLI must be on PATH and configured.
wiki version
wiki config
If wiki is not installed, install from the latest release at https://github.com/olgasafonova/mediawiki-mcp-server/releases or build from source:
go install github.com/olgasafonova/mediawiki-mcp-server/cmd/wiki@latest
If wiki config reports missing MEDIAWIKI_URL, stop and ask the user to set it (plus MEDIAWIKI_USERNAME + MEDIAWIKI_PASSWORD for write access). Do not attempt to publish.
Workflow
- Resolve the file path. If the user gave one, use it. If not, ask.
- Resolve the page title. If the user gave one, use it. Otherwise propose one from the markdown's first H1 heading; confirm before proceeding.
- Preview by default for unfamiliar files. Run
wiki publish <file> "<title>" --preview --jsonand show the user the wikitext. Skip the preview only if the user said "publish without preview" or "just push it." - Publish. Run
wiki publish <file> "<title>" --jsonwith optional flags:--summary "<text>"if the user supplied one--minorif the user flagged the change as minor--theme tieto|neutral|darkif the user specified a theme--cssto include the CSS styling block
- Report the result. Parse the JSON response and surface the revision ID and (if a new page was created) the new_page flag.
CLI contract
wiki publish <file.md> <page-title> [flags]
--summary string Edit summary (default: "Published from <basename>")
--minor Mark as minor edit
--theme string Conversion theme: neutral|tieto|dark (default: neutral)
--css Include CSS styling block
--preview Convert and print wikitext without publishing
--json Machine-readable output
JSON response on successful publish:
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.
- 12d ago First seen · 77 lines · 57 tokens per session scan A 5b26b773aa46
wiki-publish is a skill published in the GitHub repository olgasafonova/mediawiki-mcp-server (20 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 802 once invoked, about $0.0003 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-30.
Other skills, from other repositories
go-expert
Expert-level Go development with Go 1.22+ features, concurrency, standard library, and production-grade best practices. Use when the user mentions concurrency, microservices, or backend, or when the task involves idiomatic Go, goroutines and channels, context-based cancellation, or writing an HTTP server.
miro-workflow
Compose Miro boards from natural-language requests by combining tools from miro-mcp-server. Use when the user asks to set up a sprint board, retrospective, brainstorming session, user story map, kanban, or any structured Miro layout. Do NOT use for single-tool calls (create one sticky), questions about Miro the…
miro-boards
Create and manage Miro board content including stickies, shapes, connectors, diagrams, and mindmaps. Use for whiteboard collaboration, sprint planning, retrospectives, and brainstorming.
productplan-pm
Generates comprehensive workflows for product managers to manage roadmaps, OKRs, ideas, and launches in ProductPlan. Use when doing day-to-day product management work, updating feature timelines, tracking objectives, or triaging customer feedback.
productplan-workflows
Generates step-by-step workflows for managing ProductPlan roadmaps, OKRs, ideas, and launches via MCP server tools. Use when working with ProductPlan data, planning features, tracking objectives, or coordinating product launches.
productplan-customer-facing
Generates customer-ready roadmap views and launch timelines from ProductPlan for Sales and Customer Success teams. Use when preparing for customer calls, sharing product direction, or answering "when will feature X ship?" questions.