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/SPSS-MCP --skill spss-analystgit clone --depth 1 https://github.com/Exekiel179/SPSS-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/spss-mcp/spss-analyst)<a href="https://agentmods.dev/skills/exekiel179/spss-mcp/spss-analyst"><img src="https://agentmods.dev/badge/skills/exekiel179/spss-mcp/spss-analyst/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/spss-mcp/spss-analyst"><img src="https://agentmods.dev/badge/skills/exekiel179/spss-mcp/spss-analyst.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.00208 | $0.02105 |
| Opus 5 | $0.00104 | $0.01052 |
| Sonnet 5 | $0.00042 | $0.00421 |
| Haiku 4.5 | $0.00021 | $0.00211 |
Grade A, and why
spss-analyst 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- spss-analyst — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SPSS Analyst
Workflow
- Check capabilities — Call
spss_check_statusfirst to confirm SPSS batch is available. - Explore the data — For any
.savfile, callspss_file_summaryorspss_read_metadatato know variable names, types, and labels before writing syntax. - Run a smoke test before heavy or uncommon analysis — If the target procedure is cold-path, high-cost, or unfamiliar, first run a minimal baseline such as
DESCRIPTIVES,FREQUENCIES, orDISPLAY DICTIONARY. - Write syntax — Follow conventions below. See references/spss-syntax.md for full command reference.
- Execute defensively — Use the appropriate MCP tool when one exists; otherwise use
spss_run_syntaxand add optional subcommands only after the minimal command works. - Read warnings, not just success flags — A run may return output and still contain critical warning text. Treat SPSS warning blocks as syntax guidance.
- Interpret — Explain key results in plain language after output arrives.
- Archive output — After every analysis tool call that produces a
Viewer file:, immediately archive results tospss_result/. See Output Archiving below.
Reliability Rules
- Never guess variable names or data shape.
- Never jump directly to a complex procedure on the first try.
- For uncommon methods, start with the smallest valid syntax and then add print/save options.
- If SPSS says a keyword is unrecognized, rewrite the syntax to match the reported valid keywords.
- If timeout behavior looks stale, verify that repo-local
.envis actually being loaded and restart the MCP session if needed.
Core Syntax Rules
| Rule | Correct | Wrong |
|---|---|---|
| Keywords uppercase | FREQUENCIES |
frequencies |
| Period ends every command | DESCRIPTIVES VARIABLES=age. |
DESCRIPTIVES VARIABLES=age |
Subcommands start with / |
/STATISTICS=MEAN |
STATISTICS=MEAN |
| Strings in single quotes | 'myfile.sav' |
"myfile.sav" |
Comments with * |
* My comment. |
# My comment |
| Missing value code | MISSING VALUES age (99). |
— |
What ships with it
3 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.
- 12d ago First seen · 160 lines · 208 tokens per session scan A 66fb0c5e3232
spss-analyst is a skill published in the GitHub repository Exekiel179/SPSS-MCP (22 stars, last pushed 4mo ago), licensed MIT. It adds 208 tokens to every session and 2,105 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-30.
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…