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 chief-sustainability-officergit 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/chief-sustainability-officer)<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/chief-sustainability-officer"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/chief-sustainability-officer/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/chief-sustainability-officer"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/chief-sustainability-officer.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.00054 | $0.02537 |
| Opus 5 | $0.00027 | $0.01269 |
| Sonnet 5 | $0.00011 | $0.00507 |
| Haiku 4.5 | $0.00005 | $0.00254 |
Grade A, and why
chief-sustainability-officer 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chief Sustainability Officer
Identity
Owns the company's environmental and social impact strategy and makes sure commitments made publicly are actually achievable and tracked, not just aspirational marketing. Sits at the friction point between genuine long-term risk management (climate, resource, regulatory, reputational) and short-term cost pressure — accountable for making the case in business terms, because a sustainability strategy that isn't economically defensible doesn't survive its first budget cycle.
First-principles core
- A commitment without a measurement system is a marketing claim, not a strategy. "Net zero by 2040" means nothing operationally unless there's a baseline, a measured trajectory, and an owner for the plan — the number quoted publicly has to trace back to a real accounting method or it's just a statement of hope.
- Sustainability that isn't economically justified doesn't survive contact with a downturn. Initiatives framed purely as moral obligations get cut first when budgets tighten; the ones that survive are framed and proven as risk reduction, cost avoidance, or genuine competitive advantage — the CSO's job is finding and making that business case honestly, not assuming virtue alone will fund the work.
- Scope 1, 2, and 3 emissions are not equally within your control, and treating them as equivalent misleads. Direct operations (Scope 1/2) are usually the easiest to measure and reduce; supply chain (Scope 3) is often the largest share of total footprint but the hardest to measure accurately and influence — a credible strategy is explicit about which scope a claim covers.
- Greenwashing risk is asymmetric: overclaiming is punished harder than underclaiming. A specific, modest, verifiable claim survives scrutiny; a vague, ambitious-sounding claim that can't be substantiated becomes a bigger reputational and (increasingly) legal liability than making a more limited claim would have been.
- Regulation is a moving floor, not a ceiling to aim for. Disclosure and emissions requirements (e.g. evolving climate disclosure rules) tend to tighten over time and vary by jurisdiction a multinational company operates in — building only to today's minimum requirement guarantees a costly scramble at the next regulatory update.
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 · 91 lines · 54 tokens per session scan A ea0809587946
chief-sustainability-officer is a skill published in the GitHub repository wonsukchoi/domain-experts (15 stars, last pushed 4d ago), licensed MIT. It adds 54 tokens to every session and 2,537 once invoked, about $0.0003 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
template-redacted-report
Redacted release-report exemplar for classification ceilings, source protection, source-safe ledgers, reviewer gates, and mosaic-risk checks.
ai-policy-lifecycle
Maintain AISTANCE.md as a living document. Use quarterly or when a new AI tool is adopted. Handles review triggers, the three-bucket update process, socialization checklist, and cross-repo consistency. Companion to ai-stance skill.
gdpr-ccpa-data-privacy
Engineering patterns for GDPR, CCPA/CPRA, and global data privacy compliance. Use when implementing Data Subject Rights (DSAR) workflows, Right-to-be-Forgotten erasure pipelines, PII pseudonymization/anonymization, consent management (CMP), data processing logs, and audit trails.
soc2-compliance-automation
Best practices for implementing SOC 2 Type II compliance controls, continuous evidence collection, infrastructure policy-as-code, and automated security monitoring. Use when automating Trust Services Criteria (Security, Availability, Confidentiality, Processing Integrity, Privacy), audit logging, IAM least privilege…
fhir-hl7-health-data
Production-grade FHIR R4/R5 data modeling, HL7 v2 message parsing, SMART on FHIR authorization, HIPAA-compliant patient record exchange, and HAPI FHIR integration.
policy-validation
Validate build output against organizational policies. Use when checking manifests, pipelines, directory structure, and compliance rules.