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 instructions/opennem/openelectricity/agents-mdgit clone --depth 1 https://github.com/opennem/openelectricityWrote 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/instructions/opennem/openelectricity/agents-md)<a href="https://agentmods.dev/instructions/opennem/openelectricity/agents-md"><img src="https://agentmods.dev/badge/instructions/opennem/openelectricity/agents-md.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.00885 | $0.00885 |
| Opus 5 | $0.00443 | $0.00443 |
| Sonnet 5 | $0.00177 | $0.00177 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
openelectricity AGENTS.md 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 5d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open Electricity agent guide
This is the canonical guidance for any coding agent working in this repository. Platform-specific instruction files must defer to this document rather than duplicating it.
Start here
- If
personal-notes/exists, begin withpersonal-notes/PLAN.mdandpersonal-notes/TODO.mdfor the maintainer's current priorities and local working context. The directory is intentionally gitignored and may be absent. - Keep all project-specific agent memory, next actions, TODOs, and planning notes
in
personal-notes/. Do not create local planning or memory files elsewhere in the repository. - Read
README.mdfor setup anddocs/architecture.mdbefore unfamiliar work. - Preserve unrelated working-tree changes. Do not reset, reformat, or stage them.
- Prefer small, focused changes. Read the nearby code and tests before changing a subsystem.
- Use UK English in user-facing copy, documentation, and commit messages.
Commands and verification
- Use
pnpmonly. Node 22.12 or later is required. pnpm run devis the contributor path and reads.env.pnpm run doppler-devis a maintainer convenience; never make Doppler a requirement for contributors.- Run
pnpm run test:unitfor code changes. Run the narrowest relevant test first when practical. - Run
pnpm run checkafter JavaScript, TypeScript, or Svelte changes. It has a known pre-existing error baseline; do not introduce errors in files you touch. - Run
pnpm run lintwhen formatting or linting is relevant. Do not runpnpm run formatover unrelated files without permission.
Project rules
- This is Svelte 5 and SvelteKit. Use runes in new reactive code and property
event handlers such as
onclick, not legacyon:clicksyntax. - Do not introduce React-bound packages. Install framework-neutral packages
only, and add every package with
pnpm add -D. - Keep contributor
.envsupport. When adding an environment variable, update.env.exampleand explain both local.envand maintainer Doppler flows in any setup documentation you change. - Avoid new public
/api/*routes for server-only data calls; call the service directly from a server load function instead. New client-facing endpoints need validation, caching, error handling, and a documented browser caller. - Tests live next to the code they cover:
thing.jsandthing.test.js, never in a new__tests__/directory. - Generated facility OG cards are committed assets. Follow the root README's
build:oginstructions; do not regenerate them incidentally.
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.
- 5d ago First seen · 72 lines · 885 tokens per session scan A 9db719655b2f
openelectricity AGENTS.md is an instructions file published in the GitHub repository opennem/openelectricity (10 stars, last pushed 5d ago), licensed MIT. It adds 885 tokens to every session, about $0.0044 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 instructions, from other repositories
aemo-mcp CLAUDE.md
Claude Code instructions for Bigred97/aemo-mcp, covering aemo-mcp, source, curated datasets (10), repo-specific module set and repo-specific gotchas.
pocketbase-sveltekit-starter AGENTS.md
Instructions for spinspire/pocketbase-sveltekit-starter, covering agents, project structure, dev mode, deployment and key commands.
svelte-markdown CLAUDE.md
Claude Code instructions for humanspeak/svelte-markdown, covering claude.md, project overview, key technologies, project structure and development commands.
ssgoi AGENTS.md
Instructions for meursyphus/ssgoi, covering ssgoi and releasing.
sveltest AGENTS.md
AGENTS.md instructions for spences10/sveltest, covering agents.md, unbreakable rules, essential commands, development and testing.
neo-svelte copilot-instructions.md
Copilot instructions for dvcol/neo-svelte, covering examples old vs new, redirect and error handling, cookie path requirement, top-level promise handling and goto changes.