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 VandanaAjayDubey111/great-pm --skill climate-mrvgit clone --depth 1 https://github.com/VandanaAjayDubey111/great-pmWrote 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/vandanaajaydubey111/great-pm/climate-mrv)<a href="https://agentmods.dev/skills/vandanaajaydubey111/great-pm/climate-mrv"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/climate-mrv/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/vandanaajaydubey111/great-pm/climate-mrv"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/climate-mrv.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.00059 | $0.01771 |
| Opus 5.5 | $0.00024 | $0.00708 |
| Sonnet 5.5 | $0.00012 | $0.00354 |
| Haiku 4.5 | $0.00006 | $0.00177 |
Grade A, and why
climate-mrv 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 1mo 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex host binding
- Treat references to Claude slash workflows as the equivalently named Codex skill.
- Before delegating to any specialist, read the
great-pm-runtimeskill and the selected packaged role file. - Treat "invoke", "assign", "delegate", "spawn", and source Agent-tool instructions as a required Codex
spawn_agentcall with that role and a bounded assignment. - For the spawn tool's
task_nameoragent_nameidentifier, replace canonical role-name hyphens with underscores (query-refiner-pm→query_refiner_pm). Keep canonical names unchanged in prompts, filenames, verdict logs, and user-facing output; this is an internal identifier mapping, not a role rename. - Store every returned agent identifier. Never call a wait tool until a spawn has returned an identifier, and wait only on identifiers returned by successful spawns.
- If
spawn_agentis unavailable or a spawn fails, report BLOCKED; do not impersonate the specialist or wait on an empty agent set. - Resolve bundled paths from the installed GreatPM plugin root.
- Ignore Claude-only model aliases, colors, turn limits, and tool allowlists.
- Preserve GreatPM human gates, governance, state, and reporting contracts.
Climate MRV — product-side playbook
MRV = Measurement, Reporting, Verification. Climate / carbon claims must be measurable, reportable, and verifiable — increasingly required by regulation (CSRD in EU, SEC climate disclosure in US) and audited. Greenwashing penalties have arrived. PMs building climate products need this frame.
1. The three scopes (GHG Protocol)
| Scope | What | Example |
|---|---|---|
| 1 | Direct emissions from owned/controlled sources | Company-owned vehicles, on-site fuel combustion |
| 2 | Indirect emissions from purchased energy | Electricity from grid |
| 3 | All other indirect emissions in value chain | Supply chain (upstream), product use (downstream), employee commuting, business travel |
Scope 3 is usually the largest AND hardest to measure. Methodology choice (spend-based vs activity-based vs supplier-specific) matters hugely.
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.
- 1mo ago First seen · 177 lines · 59 tokens per session scan A 7c8123885f4f
climate-mrv is a skill published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 1,771 once invoked, about $0.0002 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-21.
Other skills, from other repositories
auditing-part11-trails
Generates and verifies 21 CFR Part 11-style audit trails — who/what/when, electronic signatures, and tamper-evidence — for OpenMed pipelines in GxP and clinical-trial (GCP) settings. Use when the user runs OpenMed in a regulated/validated environment and needs an attributable, time-stamped, tamper-evident record of…
generating-synthetic-surrogates
Replace detected PHI with realistic, type-matched fake values in OpenMed so clinical notes stay readable and parseable instead of full of [REDACTED] markers. Use when the user wants surrogate names, MRNs, addresses, or dates rather than opaque masks, needs consistent fake identities across a document, must keep notes…
shifting-clinical-dates
Apply consistent per-patient date shifting in OpenMed that preserves intervals between events while satisfying HIPAA Safe Harbor's date rule. Use when the user needs to de-identify dates but keep temporal structure for research, shift all dates by the same offset per patient, preserve days-between-events for survival…
fda-database
Query openFDA API for drugs, devices, adverse events, recalls, regulatory submissions (510k, PMA), substance identification (UNII), for FDA regulatory data analysis and safety research.
clinical
Clinical study design, statistical analysis, and regulatory compliance for medical research.
patent-drafting
Draft patent applications for scientific inventions, covering claims, specification, and prior art analysis.