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-operationsgit 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-operations)<a href="https://agentmods.dev/skills/olgasafonova/mediawiki-mcp-server/wiki-operations"><img src="https://agentmods.dev/badge/skills/olgasafonova/mediawiki-mcp-server/wiki-operations/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-operations"><img src="https://agentmods.dev/badge/skills/olgasafonova/mediawiki-mcp-server/wiki-operations.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.00031 | $0.00454 |
| Opus 5 | $0.00015 | $0.00227 |
| Sonnet 5 | $0.00006 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
wiki-operations 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 11d 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 Operations
Trigger
Searching, reading, or analyzing content on a MediaWiki wiki.
Workflow
-
Search for content — Use
mediawiki_searchfor full-text search across the wiki. Usemediawiki_search_in_pagewhen you know the specific page. -
Read pages — Use
mediawiki_get_pagewith the exact page title. If the title might be wrong, usemediawiki_resolve_titlefirst (handles case sensitivity and typos). -
Explore structure — Use
mediawiki_get_sectionsto see page structure,mediawiki_list_categoriesfor topic browsing,mediawiki_get_category_membersfor pages in a category. -
Check quality — Use
mediawiki_check_linksfor broken external URLs,mediawiki_find_broken_internal_linksfor broken wiki links,mediawiki_find_orphaned_pagesfor unlinked pages,mediawiki_check_terminologyfor naming consistency. -
Track changes — Use
mediawiki_get_revisionsfor page history,mediawiki_compare_revisionsfor diffs,mediawiki_get_recent_changesfor recent activity (supports aggregation by user, page, or type),mediawiki_get_user_contributionsfor a specific editor's work. -
Find related content — Use
mediawiki_get_relatedfor pages connected by categories and links,mediawiki_find_similar_pagesfor content-based similarity,mediawiki_compare_topicto see how a term is described across pages. -
Convert content — Use
mediawiki_convert_markdownto transform Markdown to wikitext. Supports themes: tieto, neutral, dark.
Guardrails
- Page titles are case-sensitive. Use
mediawiki_resolve_titlewhen unsure. - Use
mediawiki_search_in_pageinstead of fetching entire pages just to find text. - For aggregated change reports, use the
aggregate_byparameter onmediawiki_get_recent_changes.
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.
- 11d ago First seen · 33 lines · 31 tokens per session scan A 2265cd052dfc
wiki-operations is a skill published in the GitHub repository olgasafonova/mediawiki-mcp-server (20 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 454 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.