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/brensch/scadaminer-ai-toolkitWrote 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/brensch/scadaminer-ai-toolkit/nem-price)<a href="https://agentmods.dev/commands/brensch/scadaminer-ai-toolkit/nem-price"><img src="https://agentmods.dev/badge/commands/brensch/scadaminer-ai-toolkit/nem-price/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/commands/brensch/scadaminer-ai-toolkit/nem-price"><img src="https://agentmods.dev/badge/commands/brensch/scadaminer-ai-toolkit/nem-price.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.00014 | $0.00322 |
| Opus 5 | $0.00007 | $0.00161 |
| Sonnet 5 | $0.00003 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
nem-price 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.
What it actually says
The user wants NEM price data from the SCADA Miner warehouse.
Request: $ARGUMENTS
Follow the SCADA Miner workflow:
- Call
start_questionwith the user's request to open a trace, and pass the returnedquestion_idon every later tool call this turn. - Resolve any region / interconnector / station term with
search_entities. NEM regions areNSW1,QLD1,SA1,TAS1,VIC1. - Call
get_data_freshnessif the request is time-bounded, and clamp the range to available data. NEM time is Australia/Brisbane (UTC+10, no DST). Resolve any undated phrase to the most recent past occurrence and restate the year. - Call
list_capabilitiesand prefer a matching price capability viarun_capability— it returns validated SQL, a chart, and a deterministic answer. Only hand-write SQL withexecute_sqlif no capability fits. - Build a chart with
build_chart(or use the capability'schart_figure). - Answer concisely with exact numbers, the resolved date range, and any caveats.
If the region or period is missing or ambiguous, ask one clarifying question before querying.
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 · 27 lines · 14 tokens per session scan A d2f39462112f
nem-price is a command published in the GitHub repository brensch/scadaminer-ai-toolkit (0 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 322 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 commands, from other repositories
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
scan
Scan AWS account for cost optimization.
audit
Scan for non-kernel money math. Rebuild critical flows as JournalEntrys. Replay and prove. Complements /ledger-verify.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…