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 commands/vitalini/ebb-ai/gridgit clone --depth 1 https://github.com/Vitalini/ebb-aiWrote 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/vitalini/ebb-ai/grid)<a href="https://agentmods.dev/commands/vitalini/ebb-ai/grid"><img src="https://agentmods.dev/badge/commands/vitalini/ebb-ai/grid.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.00012 | $0.00772 |
| Opus 5 | $0.00006 | $0.00386 |
| Sonnet 5 | $0.00002 | $0.00154 |
| Haiku 4.5 | $0.00001 | $0.00077 |
Grade A, and why
grid 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Show current grid carbon intensity plus the next 24-hour forecast so the user can decide whether to run a workload now or wait.
Arguments
$ARGUMENTS
- Electricity Maps zone code. Common values:
US-CAL-CISO,US-TEX-ERCO,US-NE-ISNE,US-MIDA-PJM,GB,FR,DE. get_grid_forecastrequires an explicitregion. If the user gives none, derive one the same way the server derives its default: from the user's timezone (Europe/London→GB,Europe/Paris→FR,Europe/Berlin→DE,America/Los_Angeles→US-CAL-CISO,America/New_York→US-MIDA-PJM), falling back toGB— and tell the user which zone you used so they can correct it.- If the user gives a country name (e.g. "France"), translate to the zone code before calling the tool. Do not pass free-form names to the MCP server.
What to do
-
Call the
ebb-aiMCP server'sget_grid_forecasttool with:region— the parsed zone codehours— 24
-
The tool returns a plain-text report, not JSON. Its shape:
Region: <zone> Source: <source> Generated: <iso timestamp> Hour | gCO2/kWh | band --- | --- | --- HH:MM | <n> | <band> ... one row per hour ... Cleanest hour: <iso> (<n> gCO2/kWh, <band>) Dirtiest hour: <iso> (<n> gCO2/kWh, <band>)From it, compute:
- Now — the first table row (intensity + band)
- Cleanest / dirtiest hour — read the summary lines verbatim, converted to a time-from-now offset
- Average over 24h — mean of the table rows
-
Render as:
<zone> · <data source> now <intensity> g/kWh (<band>) cleanest <intensity> g/kWh (in <Xh>, <band>) dirtiest <intensity> g/kWh (in <Xh>, <band>) average <intensity> g/kWh<data source>is theSource:line — one ofelectricityMaps/ukCarbonIntensity/eia/entsoe/mock. Be honest with the user:mockmeans synthetic data (no live feed for the zone), so present the numbers as an illustrative baseline, not a measurement. -
End with a one-line recommendation:
- If
nowis incleanorvery_cleanband: "Run now — grid is already clean." - If
cleanest_hour < now * 0.7: "Defer if you can — % cleaner in ." - Otherwise: "No meaningful intraday variation — run when convenient."
- If
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 · 76 lines · 12 tokens per session scan A 328c3418fae9
grid is a command published in the GitHub repository Vitalini/ebb-ai (1 stars, last pushed 22d ago), licensed Apache-2.0. It adds 12 tokens to every session and 772 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
generate-ecosystem
Generate a validated Claude Code ecosystem (orchestrator + N sub-agents + M skills + MCPs) from a brief.
escribe-dialogo
Generates short dramatic-comedy dialogue stories between a fixed astronaut and a robot assistant from a user prompt, saved as a Markdown file. Use when the user invokes /escribe-dialogo or asks to write a space dialogue, relato, or historia with two characters.
review-pr
Reviews pull requests with three independent checkers (security, performance, tests) and aggregates findings into a single structured comment. Use when the user says "review PR", "audit diff", or "ship this", or whenever a GitHub PR URL is pasted. Does NOT modify code — it only reports findings.
add-tool
Add a new MCP tool to server.py.
add-adapter-method
Add a new method to both Airflow adapters.
check-airflow-compat
Verify code works with both Airflow 2.x and 3.x.