dirge AGENTS.md

Repository instructions for dirge-code/dirge covering how coding agents should work in that project.

In plain words
What is it for?
Use them when working in the repository to follow its agent guidance, run shell commands non-interactively, and handle forced or recursive operations correctly.
Why use it?
They provide project-specific rules for commands, file operations, and overwriting existing content.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/dirge-code/dirge/agents-md
Clone the repo
git clone --depth 1 https://github.com/dirge-code/dirge

Made for: Codex, OpenCode.

Per session 742 This file is loaded in full into every session.
When invoked 742 The same file — it is already loaded in full.
Security scan C 1 finding. Scan, not verified.
Origin unknown 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.

ModelPer sessionOnce invoked
Fable 5 $0.00742 $0.00742
Opus 5 $0.00371 $0.00371
Sonnet 5 $0.00148 $0.00148
Haiku 4.5 $0.00074 $0.00074

Measured yesterday against content hash e1419bb0720d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

dirge AGENTS.md scanned grade C with 1 finding 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 yesterday.

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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf directory # NOT: rm -r directory
AGENTS.md · 85 lines

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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.

  1. yesterday First seen · 85 lines · 742 tokens per session scan C e1419bb0720d

Subscribe to this mod's changes

dirge AGENTS.md is an instructions file published in the GitHub repository dirge-code/dirge (337 stars, last pushed 2d ago), licensed GPL-3.0. It adds 742 tokens to every session, about $0.0037 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories