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/0xdarkmatter/claude-mods/agents-mdgit clone --depth 1 https://github.com/0xDarkMatter/claude-modsWrote 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/instructions/0xdarkmatter/claude-mods/agents-md)<a href="https://agentmods.dev/instructions/0xdarkmatter/claude-mods/agents-md"><img src="https://agentmods.dev/badge/instructions/0xdarkmatter/claude-mods/agents-md.svg" alt="Measured on agentmods" 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.02482 | $0.02482 |
| Opus 5 | $0.01241 | $0.01241 |
| Sonnet 5 | $0.00496 | $0.00496 |
| Haiku 4.5 | $0.00248 | $0.00248 |
Grade A, and why
claude-mods 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 5d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
Project Overview
This is claude-mods - a collection of custom extensions for Claude Code:
- 3 expert agents for pure context-isolation/worker roles (git-agent, firecrawl-expert, project-organizer) - every domain-knowledge agent became an
-opsskill (v3.0, skills-first) - 3 commands for session management and git orchestration (/sync, /save, /git-ops)
- 103 skills for CLI tools, patterns, workflows, and development tasks (incl.
rembg-opsfor transparent-PNG cutouts of flat illustration/sticker/avatar art with a deterministic fallback ladder past rembg's ML failure modes;parallel-opsas the router for the parallel/recurring-agent-work family — fleet-ops, fleet-worker, fleetflow (extracted toX:\Forge\fleetflow, mounted as a skill via junction), loop-ops, iterate, spawn — read it first when that family is ambiguous;repo-doctorfor agentic-quality repo audits;svg-brand-tint-opsfor zero-dep in-browser SVG brand-recolour + Potrace-stage raster vectorising;r-opsfor tidyverse-first modern R / data analysis;loop-opsfor outer-loop design discipline;ffmpeg-opsfor probe-first media processing and EDL-driven editing;supply-chain-defensefor behavioural-first dependency security;prompt-injection-defensefor instruction-integrity scanning;pypi-opsfor OIDC Trusted Publishing to PyPI;net-opsfor network troubleshooting;windows-ops/mac-opsfor workstation diagnostics;fleet-workerfor cheap parallel worker delegation) - 13 output styles for response personality (Vesper, Spartan, Mentor, Executive, Pair, Atlas, Coach, Harbour, Meridian, Noir, Roast, Sage, Scout)
- 13 hooks for pre-commit linting, post-edit formatting, dangerous command warnings, uv enforcement, dependency-install + manifest-edit supply-chain advisories, hidden-Unicode scanning (session-start + pre-commit), live config-change + worktree guards, mid-session peer-writer guard + touched-files ledger, and pmail notifications - security set auto-wired via plugin hooks.json
- Pigeon inter-session messaging (
pigeon send/read/reply) - SQLite-backed pmail at~/.claude/pmail.db
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.
- 5d ago First seen · 137 lines · 2,482 tokens per session scan A ab5545ae6b3c
claude-mods AGENTS.md is an instructions file published in the GitHub repository 0xDarkMatter/claude-mods (32 stars, last pushed 13d ago), licensed MIT. It adds 2,482 tokens to every session, about $0.0124 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
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
trackly-cli CLAUDE.md
Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.
vibetags com-example-config-AsyncTestConfig.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
pupila CLAUDE.md
Instructions for FranRom/pupila, covering claude.md, where things live, stack, run locally and repo layout.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
McpServer AGENTS.md
AGENTS.md instructions for sharpninja/McpServer, covering agent instructions, session start, rules, byrd test gate and where things live.