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 EE-WILL-I/simple-data-comparator-mcp --skill json-comparatorgit clone --depth 1 https://github.com/EE-WILL-I/simple-data-comparator-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/ee-will-i/simple-data-comparator-mcp/json-comparator)<a href="https://agentmods.dev/skills/ee-will-i/simple-data-comparator-mcp/json-comparator"><img src="https://agentmods.dev/badge/skills/ee-will-i/simple-data-comparator-mcp/json-comparator.svg" alt="Measured on agentmods" 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.00049 | $0.00913 |
| Opus 5 | $0.00024 | $0.00456 |
| Sonnet 5 | $0.00010 | $0.00183 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
json-comparator 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 7d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JSON Comparator
Compare actual JSON against an expected template or JSON Schema using the validate-json MCP tool (simple-data-comparator-mcp server).
Workflow
- Discover the tool — call
GetMcpToolsfor the comparator MCP server, then invokevalidate-json. - Prepare strings — both
actualandtemplatemust be valid JSON strings (serialize objects before calling). - Call the tool with
actual(received data) andtemplate(expected data or schema). - Check
isErrorin the MCP response:false→ validation passedtrue→ read difference lines and explain mismatches to the user
- Retry with options (
strictMode,ignoreProps,ignoreSimilar, etc.) as needed.
Parameters
| Parameter | Default | Purpose |
|---|---|---|
actual |
required | JSON string to validate |
template |
required | Expected JSON template, or JSON Schema when useJsonSchema is true |
strictMode |
false |
true = fail on extra fields not in template |
ignoreArrayOrder |
false |
Sort arrays before comparing |
ignoreProps |
— | Property names stripped from both sides (e.g. ["timestamp"]) |
ignoreSimilar |
false |
Pass when values differ but JS types match |
useJsonSchema |
false |
Treat template as JSON Schema (Ajv) |
Default (strictMode: false) ignores extra fields in actual. Use strictMode: true for strict contract testing.
Interpreting results
Pass: Validation passed.
Fail:
Validation failed.
Differences:
[mismatch] age expected=30 actual=25
[missing] status expected="active" actual=undefined
[extra] city actual="NYC" expected=undefined
[schema_error] / is missing required property: age
[duplicate_key] "name" appears multiple times in the JSON
Paths use dot notation and [index] for arrays (e.g. users[0].email).
Parse error: JSON parse error: ... — fix JSON syntax before re-validating.
Example calls
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.
- 7d ago First seen · 101 lines · 49 tokens per session scan A 70d33123ac12
json-comparator is a skill published in the GitHub repository EE-WILL-I/simple-data-comparator-mcp (0 stars, last pushed 27d ago), licensed MIT. It adds 49 tokens to every session and 913 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-31.
Other skills, from other repositories
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.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.