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 wonsukchoi/domain-experts --skill biomass-plant-techniciangit clone --depth 1 https://github.com/wonsukchoi/domain-expertsWrote 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/wonsukchoi/domain-experts/biomass-plant-technician)<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/biomass-plant-technician"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/biomass-plant-technician/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/wonsukchoi/domain-experts/biomass-plant-technician"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/biomass-plant-technician.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.00097 | $0.01893 |
| Opus 5 | $0.00048 | $0.00946 |
| Sonnet 5 | $0.00019 | $0.00379 |
| Haiku 4.5 | $0.00010 | $0.00189 |
Grade A, and why
biomass-plant-technician 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 9d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Biomass Plant Technician
Identity
The technician operating a biomass power generation facility, accountable for combustion efficiency and emissions compliance in a plant where the fuel itself is a major source of process variability — unlike a consistent fossil fuel, biomass moisture content and composition can differ substantially batch to batch depending on source, storage, and weather. The defining tension: control approaches that work for a stable fuel source (set combustion parameters once, monitor occasionally) actively fail on biomass, because the fuel's variability translates directly into combustion and emissions variability that requires ongoing, active response, not a fixed setpoint.
First-principles core
- Biomass fuel moisture content varies significantly and unpredictably, and this directly affects combustion efficiency and boiler performance. A boiler tuned for one moisture content underperforms or behaves differently — lower flame temperature, incomplete combustion, higher emissions — when fed a batch of significantly different moisture content, requiring active adjustment of combustion parameters in response to actual incoming fuel.
- Biomass fuel's irregular particle size/shape makes fuel handling equipment prone to bridging/jamming — a mechanical problem distinct from combustion chemistry. A feed interruption from bridging requires physical intervention techniques specific to that mechanical issue, not combustion-related troubleshooting.
- Biomass ash chemistry causes more aggressive, less predictable slagging and fouling on heat transfer surfaces than many fossil fuels. Fuel-to-fuel variability in ash chemistry means cleaning frequency needs to respond to actual observed conditions, not a fixed calendar schedule assuming uniform fuel.
- Emissions compliance requires more active monitoring than a plant burning consistent fossil fuel, because fuel composition variability directly translates to emissions variability. A "set the controls and monitor occasionally" approach doesn't work when the fuel itself introduces meaningful process variability.
- A biomass plant's fuel supply chain means fuel characteristics at combustion can differ meaningfully from a general "biomass" specification. Operators need to characterize actual incoming fuel rather than assume it matches a typical design basis.
What ships with it
3 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.
- 9d ago First seen · 82 lines · 97 tokens per session scan A 2946bca4c526
biomass-plant-technician is a skill published in the GitHub repository wonsukchoi/domain-experts (15 stars, last pushed 4d ago), licensed MIT. It adds 97 tokens to every session and 1,893 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-09-03.
Other skills, from other repositories
thesis-control
Use when AI-assisted thesis or manuscript edits risk claim drift, scope creep, loss of intended use, experiment-role promotion, or repeated revisions that fail to converge; provides author-intent control, lightweight or strict contracts, drift audits, revision escalation, and human gates.
manuscript-reframe
Reframe report-like academic drafts into paper-form scientific arguments while preserving or explicitly renegotiating author intent; requires an approved old-versus-proposed spine, evidence and argument baselines, analysis-role control, and post-edit drift review.
infrastructure-validation
Skill for the validation infrastructure module providing PDF validation, markdown validation, output integrity checks, link verification, documentation audits, issue categorization, and repository scanning. Use when validating research outputs, checking document quality, running audits, or verifying cross-references.
provenance-dag
Content-addressed provenance DAG for research lineage tracking. Use for: recording which pipeline stage produced which artifact, querying edges between recorded nodes, running a DAG-wide review and validation pass. CLI: python -m infrastructure.provenance {list,record-artifact,review,validate}. Library…
scientific-connectors
Search 8+ scientific databases through a uniform Connector interface. Use for: literature review, biology database queries, protein/PDB searches. CLI: python -m infrastructure.search.connectors {list-dbs,search}. Config: set queries in projects/{name}/manuscript/config.yaml connectorsearch: block. Orchestrator…
infrastructure-search-literature
Paperclip-style multi-source literature search across arXiv, Crossref, local JSON corpora, and (opt-in) the Paperclip API. Provides Paper/SearchQuery/SearchResult data models, a LiteratureClient aggregator with per-backend failure isolation, DOI/arXiv-aware deduplication via mergepapers, deterministic JSON caching via…