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 agentmods add skills/rshade/finfocus/jqschemanpx skills add rshade/finfocus --skill jqschemagit clone --depth 1 https://github.com/rshade/finfocusWrote 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/rshade/finfocus/jqschema)<a href="https://agentmods.dev/skills/rshade/finfocus/jqschema"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/jqschema.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 | $0.00015 | $0.00762 |
| Opus 5 | $0.00008 | $0.00381 |
| Sonnet 5 | $0.00003 | $0.00152 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
jqschema 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 4d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jqschema - JSON Schema Discovery
Use ./.github/skills/jqschema/jqschema.sh directly from the repository skill folder to discover complex JSON structure.
Purpose
Generate a compact structural schema (keys + types) from JSON input. Use it when:
- Analyzing tool outputs from GitHub search (search_code, search_issues, search_repositories)
- Exploring API responses with large payloads
- Understanding the structure of unfamiliar data without verbose output
- Planning queries before fetching full data
Usage
# Analyze a file
cat data.json | ./.github/skills/jqschema/jqschema.sh
# Analyze command output
echo '{"name": "test", "count": 42, "items": [{"id": 1}]}' | ./.github/skills/jqschema/jqschema.sh
# Analyze GitHub search results
gh api search/repositories?q=language:go | ./.github/skills/jqschema/jqschema.sh
How It Works
The script transforms JSON data by:
- Replacing object values with their type names ("string", "number", "boolean", "null")
- Reducing arrays to their first element's structure (or empty array if empty)
- Recursively processing nested structures
- Outputting compact (minified) JSON
Example
Input:
{
"total_count": 1000,
"items": [
{"login": "user1", "id": 123, "verified": true},
{"login": "user2", "id": 456, "verified": false}
]
}
Output:
{"total_count":"number","items":[{"login":"string","id":"number","verified":"boolean"}]}
Best Practices
Use this script when:
- You need to understand the structure of tool outputs before requesting full data
- GitHub search tools return large datasets (use
perPage: 1and pipe through schema minifier first) - Exploring unfamiliar APIs or data structures
- Planning data extraction strategies
Example workflow for GitHub search tools:
# Step 1: Get schema with minimal data (fetch just 1 result)
# This helps understand the structure before requesting large datasets
echo '{}' | gh api search/repositories -f q="language:go" -f per_page=1 | ./.github/skills/jqschema/jqschema.sh
# Output shows the schema:
# {"incomplete_results":"boolean","items":[{...}],"total_count":"number"}
# Step 2: Review schema to understand available fields
# Step 3: Request full data with confidence about structure
# Now you know what fields are available and can query efficiently
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.
- 4d ago First seen · 96 lines · 15 tokens per session scan A 9fa09c6cab98
jqschema is a skill published in the GitHub repository rshade/finfocus (5 stars, last pushed 4d ago), licensed Apache-2.0. It adds 15 tokens to every session and 762 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-08-31.
Other skills, from other repositories
aws-cost-ops
AWS Cost Explorer — spending analysis, service breakdowns, forecasts, cost anomalies. Use when analyzing AWS spending, investigating cost spikes, reviewing network cost drivers like NAT Gateway, or forecasting next month's bill.
dashboards
Use when creating or extending Costory dashboards, generating interesting FinOps overviews (suggestgroupby + suggestusagemetrics + text widgets), adding or replacing widgets, copying widgets between dashboards, editing dashboardContext (global filter / period / groupBy) via updatedashboard, or applying shared-context…
reports
Use when creating, previewing, updating, scheduling, or exploring Costory reports. Route by intent: scheduled Slack/Teams/email sharing (Schedule — ask before build) vs explain last-month cost with preview-first DIGEST (Explain — chat preview required; not query+compare). Workflows are named, never lettered. DIGEST AI…
query
Use when exploring Costory cost, usage, metric, formula, budget, or external-metric data with the query tool — scope vs split (filterCel / groupBy), explorer PoP comparison, CEL discovery, unit economics, budgets. Not for one-shot "what changed last month" change trees — those use recipes explain-period-change /…
cost-change-investigation
Use when investigating a cost change to explain what changed, when, and the best-supported drivers with contribution, timing, usage, metric, event, alert, and terminology evidence. Call getskill with skillId "cost-change-investigation" before starting the investigation.
runway
Show current cloud credit and spend numbers - how much credit was granted, how much is used, how much is left, when it expires, and where the money went. Use whenever the user asks about cloud spend, cloud costs, credits, AWS/Azure/GCP spend, "how much have I spent", "how much is left", "what's my burn", "what's my…