nem-market-analysis

nem-market-analysis is a skill for Claude Code, Codex from brensch/scadaminer-ai-toolkit. It costs 103 tokens per session (870 once invoked), scanned A, original, MIT.

A guide for answering questions about Australia’s National Electricity Market (NEM) and data published by the Australian Energy Market Operator (AEMO), using the SCADA Miner data service.

In plain words
What is it for?
It helps answer questions about prices, generation, frequency control services, power transfers between regions, network limits, demand, bids and generator revenue.
Why use it?
It provides a defined process for finding the right electricity-market entities, dates and measurements instead of guessing from unfamiliar market data.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps answer questions about prices, generation, frequency control services, power transfers between regions, network limits, demand, bids and generator revenue.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/brensch/scadaminer-ai-toolkit/nem-market-analysis
Install

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.

Any agent
npx skills add brensch/scadaminer-ai-toolkit --skill nem-market-analysis
Clone the repo
git clone --depth 1 https://github.com/brensch/scadaminer-ai-toolkit

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for nem-market-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/brensch/scadaminer-ai-toolkit/nem-market-analysis/github.svg)](https://agentmods.dev/skills/brensch/scadaminer-ai-toolkit/nem-market-analysis)
Your own site
<a href="https://agentmods.dev/skills/brensch/scadaminer-ai-toolkit/nem-market-analysis"><img src="https://agentmods.dev/badge/skills/brensch/scadaminer-ai-toolkit/nem-market-analysis/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.

agentmods 80×15 button for nem-market-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/brensch/scadaminer-ai-toolkit/nem-market-analysis"><img src="https://agentmods.dev/badge/skills/brensch/scadaminer-ai-toolkit/nem-market-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 870 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00103 $0.00870
Opus 5 $0.00051 $0.00435
Sonnet 5 $0.00021 $0.00174
Haiku 4.5 $0.00010 $0.00087

Measured 11d ago against content hash 13b2ae51a7f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

nem-market-analysis 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.

skills/nem-market-analysis/SKILL.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

NEM Market Analysis (SCADA Miner)

This skill helps you answer Australian National Electricity Market (NEM) questions accurately using the SCADA Miner MCP server, which exposes a ClickHouse warehouse of AEMO market data. Apply it whenever the user asks about NEM/AEMO topics (prices, generation, FCAS, interconnectors, constraints, demand, bids, revenue) and the SCADA Miner tools are connected.

Key facts

  • NEM time is Australia/Brisbane (UTC+10, no daylight saving). Do date arithmetic in that zone.
  • Regions are NSW1, QLD1, SA1, TAS1, VIC1.
  • All warehouse access is read-only.

Workflow

  1. Open a trace. Call start_question with the user's question and pass the returned question_id on every subsequent tool call in the same answer turn.
  2. Resolve entities. For each station / DUID / region / interconnector / fuel term, call search_entities and pick the candidate that fits the question's context. Ignore weak matches for generic English words (e.g. "demand", "power").
  3. Anchor time. If the question is time-bounded, call get_data_freshness to clamp the range to available data. Resolve undated phrases (e.g. "March 3", "last week") to the most recent past occurrence and always restate the inferred year in your answer. Ask the user if a date is genuinely ambiguous.
  4. Prefer a capability. Call list_capabilities; when one matches, use run_capability (with execute: true) — it returns pre-validated SQL, a chart, and often a deterministic answer. Always prefer this over hand-written SQL.
  5. Fall back carefully. If no capability fits, locate the table with list_tables (by domain/keywords) or search_columns (by measure), then call get_table_schema and read its caveats (sign conventions, double-counting, partial coverage) before composing SQL. Execute with execute_sql. Add a time-column WHERE filter so ClickHouse can prune.
  6. Chart when it helps. Use build_chart for trends, rankings, breakdowns, and comparisons. For multi-series data set color to the category instead of drawing one line through repeated timestamps. Use one chart per period for period-over-period comparisons, each titled with its period.
  7. Answer. Concise, analyst style: cite exact numbers with units, state the resolved date range, and note caveats. Keep it brief unless detail is asked for.

Read the full file on GitHub · 66 lines

Changes

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.

  1. 11d ago First seen · 66 lines · 103 tokens per session scan A 13b2ae51a7f6

Subscribe to this mod's changes

nem-market-analysis is a skill published in the GitHub repository brensch/scadaminer-ai-toolkit (0 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 870 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens