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 skills add nimabahrami/pypsa-skills-kit --skill pypsa-market-designgit clone --depth 1 https://github.com/nimabahrami/pypsa-skills-kitWrote 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/nimabahrami/pypsa-skills-kit/pypsa-market-design)<a href="https://agentmods.dev/skills/nimabahrami/pypsa-skills-kit/pypsa-market-design"><img src="https://agentmods.dev/badge/skills/nimabahrami/pypsa-skills-kit/pypsa-market-design/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/skills/nimabahrami/pypsa-skills-kit/pypsa-market-design"><img src="https://agentmods.dev/badge/skills/nimabahrami/pypsa-skills-kit/pypsa-market-design.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.00106 | $0.00989 |
| Opus 5 | $0.00053 | $0.00495 |
| Sonnet 5 | $0.00021 | $0.00198 |
| Haiku 4.5 | $0.00011 | $0.00099 |
Grade A, and why
pypsa-market-design 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 12d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PyPSA Market Design
- PyPSA native = NODAL, perfectly competitive, marginal-cost market.
- RUN
python scripts/price_diagnostics.py solved.ncFIRST on any solved run = MILP no-duals trap detection | floor/bid-stack plausibility | zero-price share | per-branch congestion rents + system sum. - Scope: EU market architecture (FBMC | redispatch | EUR). US two-settlement / ORDC scarcity adders not covered — the nodal core + duals logic transfers, the adders don't.
- Bus marginal prices = duals of energy balance.
- Real markets = deliberate distortions of baseline -> choose + encode distortion matching study question.
Aggregation decision (single bus / merged buses)
- Safe iff intra-zone congestion non-binding for question asked.
- CHECK: what study measures (prices? RES integration? transmission need?).
- prices | congestion | redispatch as outputs -> keep nodes | calibrated zonal layout. ! copper-plate invalidates them.
- only system energy/CO2 totals -> single bus per zone OK. STATE: assumption explicitly in deliverable.
- 2 components, 1 bus, identical price exposure (battery co-located w/ PV behind one connection) -> pricing unchanged, feasibility changed (shared grid connection limit). BUILD: shared link.
Market layouts
- nodal -> full network, Lines w/ impedances, s_max_pu = security proxy.
- zonal NTC -> 1 bus/zone, Links w/ NTC capacities between zones. Crude | standard EU screening.
- zonal flow-based (FBMC) -> zone buses + PTDF constraints on critical network elements limiting net positions. READ: linopy formulation references/flow-based.md. Constraint mechanics -> pypsa-custom-constraints.
- two-stage market + redispatch -> solve zonal dispatch -> fix -> resolve nodal feasibility w/ up/down redispatch units. READ: references/flow-based.md (redispatch section).
Prices and interpretation
- n.buses_t.marginal_price = EUR/MWh dual of nodal balance.
- scarcity hours price at VOLL only if load shedding w/ VOLL cost modeled -> else infeasible instead of pricing scarcity.
- ! EU exchange bid floor = -500 EUR/MWh (DA; cap dynamic ~4-5k). Model prices below the floor = subsidy/must-run ENCODING artifact — cap the bid, never report sub-floor prices as market outcomes.
- capacity-expansion runs -> long-run-equilibrium prices (capex enters duals via binding capacity constraints) | dispatch-only runs -> short-run prices. ! never compare either 1:1 w/ day-ahead outturns w/o stating which built.
- ! committable units = MILP = NO duals -> marginal_price empty/meaningless. Two fixes: (a) native middle path
optimize(linearized_unit_commitment=True)= pure LP, live prices, fractional commitment, objective optimistic ~10-20% | (b) industry pricing run: solve MILP -> FIX commitment (committable=False + p_min_pu/p_max_pu scaled by solved status) -> re-solve LP -> duals from THAT. Non-convex costs unrecovered by LP prices = why real markets pay uplift — model prices never show it; STATE when comparing. - storage/hydro opportunity costs -> automatic via SOC constraint duals.
- congestion ECONOMICS (rents | redispatch cost | LMP decomposition | expansion ranking) -> READ references/congestion-analysis.md. Loading screens = pypsa-reporting #10.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 48 lines · 0 tokens per session scan A e6b0b11dee04
pypsa-market-design is a skill published in the GitHub repository nimabahrami/pypsa-skills-kit (23 stars, last pushed 3mo ago), licensed MIT. It adds 106 tokens to every session and 989 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-30.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…