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-editinggit 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-editing)<a href="https://agentmods.dev/skills/olgasafonova/mediawiki-mcp-server/wiki-editing"><img src="https://agentmods.dev/badge/skills/olgasafonova/mediawiki-mcp-server/wiki-editing/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-editing"><img src="https://agentmods.dev/badge/skills/olgasafonova/mediawiki-mcp-server/wiki-editing.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.00036 | $0.00399 |
| Opus 5 | $0.00018 | $0.00199 |
| Sonnet 5 | $0.00007 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
wiki-editing 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.
What it actually says
Wiki Editing
Trigger
Making changes to wiki pages: text corrections, formatting, bulk replacements, or creating new content.
Tool Selection
Pick the simplest tool that handles the edit:
| Change type | Tool |
|---|---|
| Strike out or format text (bold, italic, underline) | mediawiki_apply_formatting |
| Replace specific text on one page | mediawiki_find_replace |
| Replace a term across multiple pages | mediawiki_bulk_replace |
| Add new content or complex multi-section edits | mediawiki_edit_page |
| Upload a file from URL | mediawiki_upload_file |
Do NOT use mediawiki_edit_page for simple text changes when mediawiki_find_replace or mediawiki_apply_formatting would work.
Workflow
-
Preview first — Always use
preview=trueonmediawiki_find_replaceandmediawiki_bulk_replacebefore making changes. Show the preview to the user and get confirmation. -
Make the edit — Execute with
preview=falseafter confirmation. -
Include an edit summary — Describe what changed: "Updated version to 3.0", "Struck out former employee name", "Fixed broken internal links".
Guardrails
- Always preview destructive edits before executing them.
- Use internal wiki links
[[Page Title]], never full URLs for wiki pages. - Don't create email links for names; wiki doesn't support
mailto:properly. - Page titles are case-sensitive. Use
mediawiki_resolve_titleif unsure. - Editing requires authentication (
MEDIAWIKI_USERNAMEandMEDIAWIKI_PASSWORDenvironment variables). - All content must be in English on the wiki.
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 · 42 lines · 36 tokens per session scan A fc1008e18891
wiki-editing is a skill published in the GitHub repository olgasafonova/mediawiki-mcp-server (20 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 399 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-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.