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 fmadore/iwac-mcp-server --skill iwac-mcpgit clone --depth 1 https://github.com/fmadore/iwac-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/fmadore/iwac-mcp-server/iwac-mcp)<a href="https://agentmods.dev/skills/fmadore/iwac-mcp-server/iwac-mcp"><img src="https://agentmods.dev/badge/skills/fmadore/iwac-mcp-server/iwac-mcp/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/fmadore/iwac-mcp-server/iwac-mcp"><img src="https://agentmods.dev/badge/skills/fmadore/iwac-mcp-server/iwac-mcp.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.00173 | $0.08671 |
| Opus 5.5 | $0.00069 | $0.03468 |
| Sonnet 5.5 | $0.00035 | $0.01734 |
| Haiku 4.5 | $0.00017 | $0.00867 |
Grade A, and why
iwac-mcp 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IWAC MCP Research Workflow
Structured methodology for academic research using the IWAC MCP server's 39 tools (4 of them semantic search, which an operator can turn off). Adapted from ALA-compliant archival research practices. Applies to server v0.9.0+ — all matching is accent- and case-insensitive; result objects use short English keys (id, date, polarity, centrality, subjectivity, description_ai, url); list/search tools return a pagination envelope (count, total_matches, offset, limit, has_more, next_offset); and enumerated filters are validated (see Reading Results & Errors below). The essentials of this guidance are mirrored in the server's MCP instructions string (mcpb/src/index.ts) for skill-less clients — when updating one, update the other.
Prerequisites
Load reference files as needed, not all upfront:
- references/tools-by-phase.md — all 39 tools with parameters, defaults, and verified filter vocabularies. Read before the first search of a session.
- references/research-domains.md — French search terms and transliteration variants by domain. Read when crafting search-term variants (Extended mode, or when a Brief search comes back thin).
- references/biases-and-limitations.md — collection biases, coverage gaps, sentiment caveats. Read before writing the synthesis.
- references/capabilities-overview.md — plain-language description of the collection and recommended ways into the data. Read when the user asks what you can do (see "Capability Questions" below).
For data schema and Omeka S API details, defer to the iwac-data skill.
Capability Questions
When the user asks what you can do with IWAC ("what can you do?", "qu'est-ce que tu peux faire ?", "what's in this collection?", "how could I search this?"), do not launch the research workflow, present the depth choice, or enumerate the 38 tools. Read references/capabilities-overview.md and answer in plain language, in the user's language:
What ships with it
4 files 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.
- 5d ago Changed c2564ea8dded
- 10d ago Changed 395fc3087585
- 18d ago Changed bc43a9c88003
- 22d ago Changed · +32 lines · +15 tokens per session 4742a7fe6187
- 1mo ago Changed 2305ef0d3657
- 1mo ago First seen · 251 lines · 158 tokens per session scan A 571dae99cfe5
iwac-mcp is a skill published in the GitHub repository fmadore/iwac-mcp-server (2 stars, last pushed 5d ago), licensed MIT. It adds 173 tokens to every session and 8,671 once invoked, about $0.0007 per session on Opus 5.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
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…
opik-test
Turn a failing Opik trace (or a described failure) into a repeatable regression check — a test-suite item with the trace's input and one or two binary assertions — so a fix can be verified by the compare skill. Works over the SDK; uses the MCP write tool when connected. Returns the suite, the item, and the assertion.…
cortex-explore-memory
Explore the memory system's state, find gaps in knowledge, assess coverage, and get diagnostic information. Use when the user asks 'what does my memory look like', 'show me memory stats', 'what am I missing', 'how good is my knowledge', 'memory health', 'show coverage', 'find gaps', 'what topics are weak', or when you…
qmclaw-workbench
A local simulator for superconducting quantum-bit experiments, including measurements used to study and tune a qubit. It produces bounded synthetic results without connecting to laboratory hardware or quantum cloud services.
quantum-fermi-hubbard-vqe
A variational quantum simulation of the open-boundary Fermi–Hubbard chain, a model of particles hopping between sites and interacting when they occupy the same system. It maps the model to qubits with the Jordan–Wigner transformation and searches for a low-energy state.
quantum-grover
A Qiskit implementation of Grover's algorithm, a quantum search method that increases the chance of finding a marked item. It can explain the method, build an explicit quantum circuit, or run it with chosen inputs.