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/toni7891/deployguard/claude-mdgit clone --depth 1 https://github.com/toni7891/DeployGuardWrote 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/toni7891/deployguard/claude-md)<a href="https://agentmods.dev/instructions/toni7891/deployguard/claude-md"><img src="https://agentmods.dev/badge/instructions/toni7891/deployguard/claude-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 | $0.01454 | $0.01454 |
| Opus 5 | $0.00727 | $0.00727 |
| Sonnet 5 | $0.00291 | $0.00291 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
DeployGuard CLAUDE.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 4d 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.
- 4d ago First seen · 144 lines · 1,454 tokens per session scan A 6b2d3d4bdd85
DeployGuard CLAUDE.md is an instructions file published in the GitHub repository toni7891/DeployGuard (3 stars, last pushed 2mo ago), with no licence file. It adds 1,454 tokens to every session, about $0.0073 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-31.
Other instructions, from other repositories
superpowers-graph CLAUDE.md
Claude Code instructions for RonMizrahi/superpowers-graph, covering superpowers-graph — repository guide, sources of truth, changing the graph — the eval ships with the change and rules that are not obvious from the code.
stockbit-mcp CLAUDE.md
Claude Code instructions for INo-xious/stockbit-mcp, covering claude.md, what this is, commands, the map and three invariants. do not break them; each has a test.
agent-plugins-skills copilot-instructions.md
Copilot instructions for richfrem/agent-plugins-skills, covering copilot instructions for agent-plugins-skills, 1. think before coding, 2. simplicity first, 3. surgical changes and 4. goal-driven execution.
magi-workflow CLAUDE.md
Instructions for howar31/magi-workflow, covering what this is, slash commands, subagents, project state model and project document tiers.
chealth CLAUDE.md
Instructions for danielithomas/chealth, covering claude.md, project purpose, language & tooling, build & test and architecture.
vscode buildNext.instructions.md
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).