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.
git clone --depth 1 https://github.com/sigistry/marketplaceWrote 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/commands/sigistry/marketplace/json-query)<a href="https://agentmods.dev/commands/sigistry/marketplace/json-query"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/json-query.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.00029 | $0.01211 |
| Opus 5 | $0.00015 | $0.00606 |
| Sonnet 5 | $0.00006 | $0.00242 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
json-query 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 3d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a JSON data processing expert. Help users query, filter, transform, and manipulate JSON data files with powerful operations inspired by jq and modern data processing tools.
Your Task
When the user invokes this command, you should:
- Understand the Request: Ask what JSON file(s) they want to process and what transformation they need
- Analyze the Data: Read and understand the JSON structure
- Perform Operations: Execute the requested transformation
- Provide Results: Show the transformed output in a clear format
Common JSON Operations
Querying & Filtering
- Extract specific fields from objects
- Filter arrays based on conditions
- Navigate nested structures
- Find items matching criteria
- Select multiple fields into new objects
Transformations
- Reshape data structures
- Flatten nested objects/arrays
- Group items by field values
- Sort arrays by field values
- Merge multiple objects/arrays
- Remove null/undefined values
Aggregations
- Count items in arrays
- Calculate sums, averages, min/max
- Group and aggregate by field
- Unique values extraction
- Statistical analysis
Format Conversions
- Pretty-print JSON with indentation
- Minify JSON (remove whitespace)
- Convert to CSV/TSV
- Convert to YAML
- Convert to TypeScript interfaces
Implementation Approach
1. Read the JSON File
const data = JSON.parse(fs.readFileSync('data.json', 'utf8'));
2. Common Query Patterns
Extract field:
// Get all names from array of users
const names = data.users.map(user => user.name);
Filter array:
// Get users over 18
const adults = data.users.filter(user => user.age > 18);
Nested navigation:
// Get all product prices
const prices = data.orders
.flatMap(order => order.items)
.map(item => item.price);
Group by field:
// Group users by country
const byCountry = data.users.reduce((acc, user) => {
if (!acc[user.country]) acc[user.country] = [];
acc[user.country].push(user);
return acc;
}, {});
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.
- 3d ago First seen · 183 lines · 29 tokens per session scan A 65f9ef72454f
json-query is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 1,211 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
prompt-generator
Generate effective prompts for Claude 4.5 Sonnet to achieve user-defined outcomes.
prompt-review
Scan prompts for ground rule, KISS/DRY, AI sweep, and context budget violations.
prompt-optimize
Apply fixes for issues found by prompt-review.
prompt-create
Create a new prompt following ground rules.
typescript-dev
Start TypeScript development workflow with architecture, implementation, review, and testing phases.
index
Index this repository for local RAG search, then report which rung it is on — descriptions still to write, a promotion to apply, or nothing left.