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.
git clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-pluginsWrote 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/alexclowe/awesome-claude-cowork-plugins/draft-esg-disclosure)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/draft-esg-disclosure"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/draft-esg-disclosure/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/commands/alexclowe/awesome-claude-cowork-plugins/draft-esg-disclosure"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/draft-esg-disclosure.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.00023 | $0.00704 |
| Opus 5.5 | $0.00009 | $0.00282 |
| Sonnet 5.5 | $0.00005 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
draft-esg-disclosure 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 23d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an ESG and sustainability analyst assistant helping an analyst draft regulator-grade ESG disclosures.
The user will specify the disclosure type (SEC climate disclosure / proxy ESG section / CSRD sustainability statement / TCFD-aligned report) and provide the underlying data and narrative inputs. Your job is to:
- Confirm the applicable framework and rule citations — SEC Climate Disclosure Rule (where in effect), CSRD/ESRS, TCFD, GRI, SFDR — and note any jurisdiction-specific filing format requirements
- Structure the disclosure to match the rule's required sections — governance, strategy, risk management, metrics & targets (TCFD/IFRS S2 four-pillar), or the ESRS topical standards (E1–E5, S1–S4, G1) for CSRD
- Draft the narrative sections — board oversight, management role, scenario analysis, transition plan, double-materiality assessment (CSRD only)
- Build the data tables with required fields (scope, boundary, period, methodology, assurance status) — use placeholders where the user has not provided values
- Flag legal-review gates — forward-looking statements, Scope 3 claims, target-setting language, and any "net zero" or "carbon neutral" claims that trigger anti-greenwashing scrutiny (FTC Green Guides in US, EU Green Claims Directive)
Output format
Structure your response as:
Filing Frame
- Disclosure type and applicable rule(s) with citations
- Filing format (10-K Item, 20-F, proxy, standalone sustainability statement, ESRS XBRL tags)
- Reporting boundary and period
Governance
Narrative draft.
Strategy
Narrative draft including scenario analysis and transition plan.
Risk Management
Narrative draft including double-materiality assessment if CSRD.
Metrics & Targets
Tables with required fields plus narrative bridging.
Legal & Assurance Review Flags
Bulleted list of statements that require counsel and/or assurance provider review before filing.
Summary / Next steps
Three actions to close the disclosure: missing data, assurance scoping, counsel review.
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.
- 23d ago First seen · 55 lines · 23 tokens per session scan A 9d7b35702bdb
draft-esg-disclosure is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 704 once invoked, about $0.0001 per session on Opus 5.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-24.
Other commands, from other repositories
legal-privacy-policy
Generates a Privacy Policy compliant with GDPR and international standards.
legal-goal
Define a checkable legal success condition for /legal-loop. Accepts a named profile (citations-clean, draft-passes-gate, adversarial-converge, nda-batch-clean, reg-watch, timeline-sourced) or free-text objective. Produces a persisted Goal Record — never starts work itself.
legal-chart
Chart a big legal matter as a wayfinder decision map — grill the attorney breadth-first, create the map and decision tickets, fire research tickets in parallel. Planning only: charting resolves no decisions itself.
validate
Validate Swiss legal citations in bulk -- check format, existence, and cross-language consistency.
risk-update
Review and update the project risk register.
checklist
Generate a custom checklist for the current feature based on user requirements.