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/brainbytes-dev/everything-claude-finance/esg-reportgit clone --depth 1 https://github.com/brainbytes-dev/everything-claude-financeWrote 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/brainbytes-dev/everything-claude-finance/esg-report)<a href="https://agentmods.dev/commands/brainbytes-dev/everything-claude-finance/esg-report"><img src="https://agentmods.dev/badge/commands/brainbytes-dev/everything-claude-finance/esg-report.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.00007 | $0.01497 |
| Opus 5 | $0.00003 | $0.00749 |
| Sonnet 5 | $0.00001 | $0.00299 |
| Haiku 4.5 | $0.00001 | $0.00150 |
Grade A, and why
esg-report 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 4d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/esg-report — ESG Analysis and Reporting
What This Command Does
Performs ESG (Environmental, Social, Governance) analysis and generates sustainability reporting aligned with major frameworks. Assesses ESG risks, scores performance against benchmarks, identifies improvement areas, and produces disclosure-ready content for regulatory and voluntary reporting.
When to Use
- Annual sustainability report preparation
- CSRD compliance (EU mandatory from 2024+)
- SFDR fund-level reporting (Article 6/8/9)
- TCFD climate risk disclosure
- ESG due diligence for investments
- Board ESG governance reporting
How It Works
- Materiality Assessment: Identifies material ESG topics through double materiality lens
- Data Collection: Maps available ESG data against framework requirements
- Scoring: Rates performance on each material topic (1-5 scale)
- Gap Analysis: Identifies disclosure and performance gaps against framework requirements
- Risk Assessment: Maps ESG risks to financial impact (transition risks, physical risks)
- Report Generation: Produces framework-aligned disclosure content
Example Usage
Input:
/esg-report entity:"NordPack Industries" framework:csrd scope:full
Output:
# ESG Report — NordPack Industries
## Framework: CSRD/ESRS | Scope: Full | Date: 2026-03-14
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Double Materiality Assessment
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
| ESRS Topic | Impact Mat. | Financial Mat. | Overall |
|-------------------------|-------------|----------------|-----------|
| E1: Climate change | High | High | Material |
| E2: Pollution | Medium | Medium | Material |
| E3: Water | Low | Low | Not material |
| E5: Resource use | High | Medium | Material |
| S1: Own workforce | Medium | Medium | Material |
| S2: Value chain workers | Medium | Low | Borderline|
| G1: Business conduct | Medium | High | Material |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Environmental (E)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
### E1: Climate Change
| Metric | 2024 | 2025 | Target 2030 | Status |
|------------------------------|--------|--------|-------------|---------|
| Scope 1 emissions (tCO2e) | 12,500 | 11,800 | 7,500 | ↗ On track |
| Scope 2 emissions (tCO2e) | 8,200 | 6,100 | 2,000 | ↗ On track |
| Scope 3 emissions (tCO2e) | 45,000 | 44,200 | 30,000 | → Needs work |
| Energy intensity (MWh/EUR M) | 85 | 78 | 50 | ↗ On track |
| Renewable energy share | 42% | 58% | 100% | ↗ On track |
Transition risk: Medium — carbon pricing exposure EUR 1.2M/yr at EUR 100/t
Physical risk: Low — no facilities in high-risk climate zones
### E5: Resource Use & Circular Economy
| Metric | 2024 | 2025 | Target 2030 |
|---------------------------|--------|--------|-------------|
| Recycled input materials | 35% | 42% | 75% |
| Waste to landfill (tonnes)| 2,800 | 2,200 | 500 |
| Packaging recyclability | 68% | 75% | 95% |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Social (S)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
### S1: Own Workforce
| Metric | 2024 | 2025 | Target |
|---------------------------|--------|--------|------------|
| Headcount | 1,250 | 1,320 | — |
| Gender diversity (mgmt) | 28% | 32% | 40% by '28 |
| Pay gap (adjusted) | 4.2% | 3.1% | < 2% by '27|
| LTIR (injury rate) | 2.8 | 2.1 | < 1.5 |
| Training hours/employee | 24 | 28 | 40 |
| Employee turnover | 14% | 12% | < 10% |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Governance (G)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
### G1: Business Conduct
| Area | Status | Comment |
|---------------------------|------------|-----------------------------|
| Anti-corruption policy | ✓ In place | Last updated Q4 2025 |
| Whistleblower mechanism | ✓ In place | EU Directive compliant |
| Supplier code of conduct | ⚠ Partial | 72% of suppliers signed |
| Board ESG oversight | ✓ In place | Sustainability committee |
| ESG-linked compensation | ⚠ Partial | CEO only — expand to C-suite|
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## CSRD Readiness Score
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
| ESRS Standard | Readiness | Key Gap |
|---------------|-----------|--------------------------------|
| ESRS 2 (General) | 75% | Value chain mapping incomplete |
| ESRS E1 | 80% | Scope 3 methodology needs work |
| ESRS E5 | 65% | Circular economy targets weak |
| ESRS S1 | 70% | Pay equity disclosure gaps |
| ESRS G1 | 60% | Supply chain due diligence |
Overall readiness: 70% — on track for FY2026 mandatory reporting.
### Priority Actions
1. Complete Scope 3 emissions inventory (GHG Protocol)
2. Expand supplier code of conduct coverage to 95%
3. Link ESG KPIs to executive compensation across C-suite
4. Establish circular economy targets with quantified milestones
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.
- 4d ago First seen · 142 lines · 7 tokens per session scan A 70b87130533a
esg-report is a command published in the GitHub repository brainbytes-dev/everything-claude-finance (5 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 1,497 once invoked, about $0.0000 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.