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 alexclowe/awesome-copilot-cowork-plugins --skill carbon-accounting-automationgit clone --depth 1 https://github.com/alexclowe/awesome-copilot-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/skills/alexclowe/awesome-copilot-cowork-plugins/carbon-accounting-automation)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/carbon-accounting-automation"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/carbon-accounting-automation/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/alexclowe/awesome-copilot-cowork-plugins/carbon-accounting-automation"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/carbon-accounting-automation.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.00028 | $0.00783 |
| Opus 5 | $0.00014 | $0.00392 |
| Sonnet 5 | $0.00006 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
carbon-accounting-automation 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 12d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You have deep expertise in corporate carbon accounting per the GHG Protocol. When the user is working on ESG sustainability tasks involving emissions data, apply this knowledge automatically.
Core competencies
GHG Protocol fundamentals:
- Scope 1 — direct emissions from owned/controlled sources (stationary combustion, mobile combustion, process emissions, fugitive emissions)
- Scope 2 — indirect emissions from purchased energy. Always report BOTH location-based (grid average) AND market-based (contractual instruments like RECs/GOs) per the Scope 2 Guidance (2015)
- Scope 3 — 15 categories across upstream (1–8: purchased goods, capital goods, fuel & energy, upstream transport, waste, business travel, employee commuting, upstream leased) and downstream (9–15: downstream transport, processing, use of sold products, end-of-life, downstream leased, franchises, investments)
Boundaries and consolidation:
- Operational control vs financial control vs equity share — choose one and apply consistently
- Document the organizational boundary; note acquisitions, divestitures, and structural changes that trigger baseline recalculation per the GHG Protocol's recalculation policy (>5% threshold typical)
Calculation methods:
- Activity data × emission factor (Tier 1) — most common for Scope 1 stationary combustion using DEFRA, EPA, or IEA factors
- Direct measurement (Tier 3) — for refineries, cement, steel where CEMS data exists
- Spend-based vs activity-based for Scope 3 — spend-based is acceptable for early inventories but activity-based / supplier-specific is required for credible decarbonization tracking
- Use the latest GWP values (currently AR6, GWP100) unless reporting under a regime that specifies an earlier set (some regimes still cite AR5)
Data quality:
- Pedigree matrix (activity-data quality, emission-factor representativeness, geographic specificity, technological specificity, temporal alignment)
- Flag missing categories, especially Scope 3 categories 1, 11, and 15 (often material)
- Note assurance status — limited assurance is the floor for CSRD; reasonable assurance phasing in
Targets:
- SBTi pathways — 1.5°C aligned (most stringent), well-below-2°C, and FLAG (Forest, Land, and Agriculture) sector
- Near-term (5–10y) vs long-term (2050 net-zero) targets — net-zero requires 90%+ absolute reduction with limited residual offsets
- Distinguish absolute reduction targets from intensity targets
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.
- 12d ago First seen · 49 lines · 28 tokens per session scan A ec9c44c6e758
carbon-accounting-automation is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (17 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 783 once invoked, about $0.0001 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
pre-submission-reviewer
Runs a pre-submission review of a technical paper across five dimensions: macro logic, writing details, English grammar, LaTeX formatting, and figure quality. Uses a reviewer-style severity taxonomy (CRITICAL / MAJOR / MINOR) and flags banned AI-tone vocabulary and em-dash misuse. Use when the user asks to 'review…
intro-drafter
Drafts the Introduction prose for a technical paper, guided internally by a six-paragraph flowchart: background and running example, existing limitations, problem essence and goal, key challenges, solution overview, contributions. Positions the paper as Technique or New Problem/Setting, aligns contributions with…
tech-paper-template
Structures a technical paper's full logical skeleton using a thinking-template table (research background, limitations, key idea or goal, challenges, methodology modules, contributions), positions the paper as Technique or New Problem/Setting, and runs a four-point self-consistency check. Use when the user is…
Full-empirical-analysis-skill
Classical end-to-end empirical analysis workflow in the traditional Python econometric stack — pandas + numpy + scipy + statsmodels + linearmodels + pyfixest + rdrobust + econml + causalml + matplotlib/seaborn. Defaults to economics empirical-paper style (AER / QJE / AEJ) — every run produces a publication-ready…
data-scientist
Data science methodology for Python research: EDA, validation, causal inference (IV, DiD, RD, synthetic control), clustering/PCA/UMAP, supervised ML, geospatial, visualization. Method selection guidance. For syntax, load tool-specific skills.
empirical-playbook
This skill covers applied microeconomic empirical methods and research design. Use when the user is selecting an identification strategy, comparing estimators, running diagnostics, designing a research study, or evaluating an empirical strategy. Triggers on "which method", "what estimator", "how to choose", "method…