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 instructions/mergifyio/mergify-cli/agents-mdgit clone --depth 1 https://github.com/Mergifyio/mergify-cliWhat 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.03339 | $0.03339 |
| Opus 5 | $0.01670 | $0.01670 |
| Sonnet 5 | $0.00668 | $0.00668 |
| Haiku 4.5 | $0.00334 | $0.00334 |
Grade A, and why
mergify-cli 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 2d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
mergify is a native Rust CLI — a Cargo workspace under crates/, with the
binary built from crates/mergify-cli ([[bin]] name = "mergify"). There is no
Python: the port is complete and every command runs in-process. If you find a
doc, comment, or rule mentioning console_error, click, DYMGroup,
mergify_cli.dym, crates/mergify-py-shim, or a "Python shim", it is stale —
fix it.
The bar is ruff/uv-grade Rust: typed errors, no panics in library code, clippy pedantic clean, snapshot-tested output. Concrete rules follow.
Workspace layout
mergify-core— shared foundations:CliError/ExitCode, the HTTPClient,auth,Output,env.mergify-tui— terminal primitives:Theme(color), glyphs, relative time. Stays dependency-light and clap-free.mergify-cli— the binary: clap tree, dispatch,run_native,self_update,cli_schema.mergify-stack/mergify-ci/mergify-queue/mergify-events/mergify-freeze/mergify-config— one crate per command group.mergify-eventsalso hosts the shared/logsclient thequeuecrate's dequeue diagnosis consumes.mergify-test-support— shared test scaffolding (not published).
Error handling
Library and command code never prints errors and never calls process::exit.
Return Result<_, mergify_core::CliError>. main() is the single error sink: it
writes mergify: {err} to stderr, walks the source() chain printing each cause
as a caused by: line, and exits with err.exit_code().
CliError is a typed enum; each variant maps to a stable ExitCode
(GitHubApi→5, MergifyApi→6, Configuration→7, … see exit_code.rs). Pick the
variant whose exit code matches the failure class. Never add a String catch-all
for a new failure category that deserves its own code — add a variant.
// GOOD — typed variant, lowercase message, no prefix (the sink adds "mergify:")
return Err(CliError::StackNotFound(format!("branch {name} not found")));
// BAD — printing + exiting inside a command
eprintln!("error: branch not found");
std::process::exit(1);
// BAD — capitalized / pre-prefixed (the sink double-prefixes it)
return Err(CliError::Generic("Error: branch not found".into()));
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.
- 2d ago First seen · 258 lines · 3,339 tokens per session scan A c24ee0e3388a
mergify-cli AGENTS.md is an instructions file published in the GitHub repository Mergifyio/mergify-cli (29 stars, last pushed 4d ago), licensed Apache-2.0. It adds 3,339 tokens to every session, about $0.0167 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.