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/darkly-art/darkly/agents-mdgit clone --depth 1 https://github.com/darkly-art/darklyWhat 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.05187 | $0.05187 |
| Opus 5 | $0.02593 | $0.02593 |
| Sonnet 5 | $0.01037 | $0.01037 |
| Haiku 4.5 | $0.00519 | $0.00519 |
Grade A, and why
darkly 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 290 lines · 5,187 tokens per session scan A 6766c09bd53a
darkly AGENTS.md is an instructions file published in the GitHub repository darkly-art/darkly (313 stars, last pushed 3d ago), with no licence file. It adds 5,187 tokens to every session, about $0.0259 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
p5.js AGENTS.md
AGENTS.md instructions for processing/p5.js, covering detailed guidelines for ai coding assistants and agents, generating any analysis of the codebase, stop signs for agents, character and tone and who you are in this conversation.
processing4 AGENTS.md
AGENTS.md instructions for processing/processing4, covering our policy, guidelines for generating any analysis of the codebase, guidelines for ai coding assistants and agents, helping human contributors (for ai coding assistants) and 2. check if the issue is ready to be worked on.
efecto-plugin AGENTS.md
AGENTS.md instructions for pablostanley/efecto-plugin, covering efecto — agent instructions, setup, mcp server, workflow and skills.
supabase studio-shortcuts.instructions.md
Instructions for supabase/supabase, covering studio shortcut review rules, core principle, when to flag, preferred pattern and search inputs.
vscode accessibility.instructions.md
Use when implementing accessibility features, ARIA labels, screen reader support, accessible help dialogs, or keybinding scoping for accessibility. Covers AccessibleContentProvider, CONTEXTACCESSIBILITYMODEENABLED, verbosity settings, and announcement patterns.
ui-components AGENTS.md
Instructions for starc007/ui-components, covering beui v2 — agent guide, commands, layout, component catalog and components (motion category — primitives).