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-sector-couplinggit 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-sector-coupling)<a href="https://agentmods.dev/skills/nimabahrami/pypsa-skills-kit/pypsa-sector-coupling"><img src="https://agentmods.dev/badge/skills/nimabahrami/pypsa-skills-kit/pypsa-sector-coupling/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-sector-coupling"><img src="https://agentmods.dev/badge/skills/nimabahrami/pypsa-skills-kit/pypsa-sector-coupling.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.00096 | $0.00698 |
| Opus 5 | $0.00048 | $0.00349 |
| Sonnet 5 | $0.00019 | $0.00140 |
| Haiku 4.5 | $0.00010 | $0.00070 |
Grade A, and why
pypsa-sector-coupling 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.
How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PyPSA Sector Coupling
Grammar: Bus per carrier per location | Link = universal converter | Store = carrier inventory. Most bugs = one of these misused.
The three patterns
- converter = Link (elec -> heat | elec -> H2 | H2 -> elec). ! efficiency > 1 legal ONLY for un-modeled environmental energy harvest (heat pump COP); otherwise = free-energy bug -> pypsa-physical-realism flags it.
- multi-output converter = Link + bus2/efficiency2 (+ bus3...). Cases: CHP (elec + heat) | electrolyzer + heat recovery | Fischer-Tropsch (fuel + heat). efficiency_i = output_i per unit bus0 input.
- CO2 accounting: BUILD explicit CO2 buses where CCS | DAC | synfuels appear. CO2 as output -> negative efficiency to "co2 atmosphere" store = standard PyPSA-Eur trick.
- inventory = Store on carrier bus (heat tank | H2 cavern | EV fleet battery state). SET standing_loss for thermal decay.
Carrier/bus design rules
- one heat bus per temperature level. ! residential ~60°C != industrial steam — never one bus.
- one H2 bus per location -> connect via pipeline Links (efficiency ~1 minus compression elec as separate input) | shipping chains.
- ! never put carrier-X demand on carrier-Y bus "because it balances" -> prices + statistics meaningless.
Reference routing — READ before modeling sector
- heating -> references/heating.md: heat pumps (time-varying COP) | resistive heaters | TES | CHP back-pressure | district heating topology | building retrofits as virtual generators.
- hydrogen -> references/hydrogen.md: electrolysis/storage/reconversion chains | cavern vs tank | pipelines | derived fuels (NH3, methanol, FT).
- transport -> references/transport.md: EV fleets | charging availability | V2G | demand-side response as shiftable load.
- industry -> references/industry-biomass-ccs.md: process heat/feedstock demand | biomass potentials as constrained Generators/Stores | CCS + DAC chains.
Cross-skill handoffs
- operational coupling (CHP feasibility polygon | electrolyzer min load | EV charging windows) = constraints -> pypsa-custom-constraints.
- plausible COPs | efficiencies | losses -> pypsa-physical-realism ranges files. Its validator WARNs: CO2-chain tech (CCS|DAC|synfuels) w/o explicit co2 bus (Link carrier co2_emissions NOT counted by GlobalConstraints) | >1 heat load carrier per bus.
- COP/heat-demand time series generation -> pypsa-data-pipelines (atlite-heat.md).
- LCOH | heat-pump-vs-boiler business cases -> pypsa-asset-economics.
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.
- 11d ago First seen · 37 lines · 0 tokens per session scan A 60123628b083
pypsa-sector-coupling is a skill published in the GitHub repository nimabahrami/pypsa-skills-kit (23 stars, last pushed 2mo ago), licensed MIT. It adds 96 tokens to every session and 698 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…
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.
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…
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…