What is climate AGENTS.md?

A set of contribution instructions for a software repository, including the required order for designing, documenting, testing, implementing, and checking a feature.

Use it when adding features or changing commands in the repository. It also explains which local checks and continuous-integration checks must pass before and after a change is considered complete.

It gives contributors a shared process and quality checklist, so important design notes, tests, documentation, and verification are less likely to be skipped.

How disk0Dancer/climate configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to disk0Dancer/climate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/disk0Dancer/climate/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/disk0Dancer/climate

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/disk0dancer/climate/agents-md/github.svg)](https://agentmods.dev/instructions/disk0dancer/climate/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/disk0dancer/climate/agents-md"><img src="https://agentmods.dev/badge/instructions/disk0dancer/climate/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/disk0dancer/climate/agents-md"><img src="https://agentmods.dev/badge/instructions/disk0dancer/climate/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 580 This file is loaded in full into every session.

When invoked 580 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00580	$0.00580
Opus 5.5	$0.00232	$0.00232
Sonnet 5.5	$0.00116	$0.00116
Haiku 4.5	$0.00058	$0.00058

Measured 2mo ago against content hash e3cfa1a3453d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

climate AGENTS.md 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 2mo 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.

AGENTS.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS contribution workflow

This repository uses an implementation-first workflow for all feature work.

Required sequence for any feature

Design first
- Describe problem, goals, non-goals, API/CLI UX, and edge cases.
- Add or update design docs in docs/.
Document behavior
- Update user-facing docs (README.md, docs/index.md) when commands or capabilities change.
Write tests
- Add targeted unit tests for new logic before/with implementation.
Implement code
- Keep changes surgical and consistent with existing project style.
Update skills
- Update skills/climate.md and skills/climate-generator/SKILL.md when command set or workflows change.
Validate locally
- Run make verify (fmt-check + vet + build + lint + go test -race). This mirrors the CI pipeline and is mandatory before every push.
- Run targeted tests during development for faster feedback.
Validate CI health
- Ensure PR checks are green before merge.
- After merge, confirm CI on main is green: gh run list --branch main --workflow CI --limit 1.
- A task is not done until post-merge CI on main is green. If it is red, fixing it is part of the same task — do not stop or hand off.
Commit discipline
- Small, meaningful commits with clear messages.
Push and PR hygiene
- Push branch updates, keep PR description/checklist current, and respond to review comments with the commit hash that addresses each request.

Quality rules

Do not remove or weaken unrelated tests.
Tests must be hermetic: they must not depend on the developer's machine or global state. Tests that shell out to external tools (e.g. git) must set the environment explicitly (t.Setenv for GIT_AUTHOR_*/GIT_COMMITTER_*, temp HOME, etc.) so they pass on a bare CI runner. "Passes on my machine" is not evidence.
Do not introduce breaking CLI changes without docs + migration notes.
Prefer deterministic behavior (sorted output, stable iteration).
Keep generated/manifest behavior backward compatible where practical.

Read the full file on GitHub · 57 lines

Changes

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.

2mo ago First seen · 57 lines · 580 tokens per session scan A e3cfa1a3453d

Subscribe to this mod's changes

climate AGENTS.md is an instructions file published in the GitHub repository disk0Dancer/climate (6 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 580 tokens to every session, about $0.0023 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-08-31.

agent-skill agent-skills ai-tools cli-generator go openapi

climate AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
climate AGENTS.mddisk0Dancer/climate	Instructions file	6	3mo ago	Apache-2.0	A	580	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

climate: Instructions file for Codex