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 Exekiel179/MNE-MCP --skill mne-writeupgit clone --depth 1 https://github.com/Exekiel179/MNE-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/exekiel179/mne-mcp/mne-writeup)<a href="https://agentmods.dev/skills/exekiel179/mne-mcp/mne-writeup"><img src="https://agentmods.dev/badge/skills/exekiel179/mne-mcp/mne-writeup/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/exekiel179/mne-mcp/mne-writeup"><img src="https://agentmods.dev/badge/skills/exekiel179/mne-mcp/mne-writeup.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.00207 | $0.01279 |
| Opus 5 | $0.00103 | $0.00639 |
| Sonnet 5 | $0.00041 | $0.00256 |
| Haiku 4.5 | $0.00021 | $0.00128 |
Grade A, and why
mne-writeup 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MNE Write-up (verified results → manuscript)
The back end of the analysis suite: after the per-category skills have run and
mne-methodology-critic has ruled, this skill writes the result up. It mirrors the ARS
academic-paper workflow (config → outline → draft → citation/integrity → format) but is specialised
for neurophysiology and is gated by the critic.
Companion:
mne-methodology-critic(the gate); the per-category analysis skills (the source of results);mne-analyst(the archiving convention this reads from). For a full multi-section paper with literature search and peer review, hand off to the ARSacademic-paper/academic-pipelineskills — this skill specialises in the Methods + Results of an MNE study.
⚠️ IRON RULES
- Only write what PASSED. A result the critic marked BLOCK is not reported as a finding; either fix-and-re-critique first, or move it to Limitations as an acknowledged problem. WARN items must appear as explicit qualifications/limitations, never silently dropped.
- Every number traces to an artifact. Each reported statistic must come from a file under
stats/(or the analysis tool's output) — never invent or round-guess a value. If it isn't in an artifact, it isn't written. - Methods must be reproducible. Pull exact parameters from the equivalent code archived in
mne_result/(filter band, reference, ICA method/components removed, epoch window, rejection threshold, TFR/connectivity/decoding settings, software versions). Vague methods = rejected.
Workflow
1. CONFIG (intake)
Confirm: output target (full paper / Methods+Results section / report), discipline + venue, citation
format (APA 7 default), language (and whether a bilingual abstract is needed), output format
(Markdown → DOCX via Pandoc). Locate the project layout (see references/writeup-guide.md): data/,
mne_result/, stats/, critic/, paper/.
2. INTAKE & GATE
Read critic/ verdicts. Build a result inventory: each finding → its figure(s) in mne_result/, its
numbers in stats/, and its critic verdict. Drop/flag BLOCKed claims (IRON RULE 1). List exactly
what will be reported and what becomes a limitation.
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.
- 11d ago First seen · 83 lines · 207 tokens per session scan A 52a6859f931b
mne-writeup is a skill published in the GitHub repository Exekiel179/MNE-MCP (7 stars, last pushed 2mo ago), licensed MIT. It adds 207 tokens to every session and 1,279 once invoked, about $0.0010 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
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…