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/deployhq/deployhq-cli/agents-mdgit clone --depth 1 https://github.com/deployhq/deployhq-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.00004 | $0.00004 |
| Opus 5 | $0.00002 | $0.00002 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00000 |
Grade A, and why
deployhq-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 today.
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.
- today First seen · 1 lines · 4 tokens per session scan A 6ebdb617a810
deployhq-cli AGENTS.md is an instructions file published in the GitHub repository deployhq/deployhq-cli (0 stars, last pushed 13d ago), with no licence file. It adds 4 tokens to every session, about $0.0000 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
Tracely-ai CLAUDE.md
Claude Code instructions for Jwuthri/Tracely-ai, covering claude.md, commands, architecture, hard rules and gotchas.
cs CLAUDE.md
Instructions for boyter/cs, covering claude.md, project overview, build & test commands, architecture and query pipeline (pkg/search/).
devopness AGENTS.md
Instructions for devopness/devopness, covering agents, core flow, shared constraints, monorepo structure and git workflow.
hana-developer-cli-tool-example command-documentation.instructions.md
Use when creating or updating CLI command documentation in docs/02-commands/. Generates comprehensive markdown files with Mermaid diagrams showing command flow, detailed parameter tables organized by category, syntax examples, and related commands.
hana-developer-cli-tool-example mcp-server-development.instructions.md
Use when creating or updating MCP (Model Context Protocol) server components. Enforces TypeScript patterns, JSON-RPC communication rules, tool/resource/prompt registration, and integration with CLI command metadata. Ensures MCP server follows protocol requirements and maintains consistency with the CLI infrastructure.
hana-developer-cli-tool-example route-development.instructions.md
Use when creating or updating route files in routes/. Enforces consistent structure, error handling, database connection management, internationalization, and integration with the Express server and CLI command infrastructure. Ensures routes follow established patterns for endpoint registration, response formatting…