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/debba/gitdeck/agents-mdgit clone --depth 1 https://github.com/debba/gitdeckWhat 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.00173 | $0.00173 |
| Opus 5 | $0.00086 | $0.00086 |
| Sonnet 5 | $0.00035 | $0.00035 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
gitdeck 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.
What it actually says
Agent Rules
- Keep all code identifiers, comments, filenames, and documentation in English.
- Preserve the current visual layout unless a task explicitly asks for UI changes.
- Prefer React components for rendering and keep component files focused on one responsibility.
- Put pure business logic in
src/utilsand cover it with unit tests under the mirroredtests/utilspath. - Keep tests outside
src; thetestsfolder must sit at the repository root and mirror the relevantsrcstructure. - Do not mix unrelated refactors with feature work.
- Use TypeScript for new source files unless an existing JavaScript integration requires otherwise.
- Keep GitHub API and
ghCLI access behind server-side endpoints; do not expose tokens to the browser. - Run
npm testandnpm run buildafter behavior changes when dependencies are available.
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 · 12 lines · 173 tokens per session scan A b603dd9f3dae
gitdeck AGENTS.md is an instructions file published in the GitHub repository debba/gitdeck (399 stars, last pushed 11d ago), licensed MIT. It adds 173 tokens to every session, about $0.0009 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
DevoxxGenieIDEAPlugin GEMINI.md
Instructions for devoxx/DevoxxGenieIDEAPlugin, a project described as: DevoxxGenie is an agentic plugin for IntelliJ IDEA that uses local LLM's (Ollama, LMStudio, GPT4All, Jan and Llama.cpp) and Cloud based LLMs to help review, test, explain your project code. Latest version now also supports Spec Driven Development…
squarebox CLAUDE.md
Instructions for SquareWaveSystems/squarebox, covering claude.md, agent skills, issue tracker, triage labels and domain docs.
mcpelevator CLAUDE.md
Instructions for pacnpal/mcpelevator, covering commands, architecture, conventions, agent skills and issue tracker.
clawchat-plugin-connect AGENTS.md
Instructions for XMethues/clawchat-plugin-connect, covering agent skills, issue tracker, triage labels and domain docs.
autonomous-dev CLAUDE.md
Claude Code instructions for akaszubski/autonomous-dev, covering autonomous-dev, critical rules, maintainer escape hatches, architecture and code navigation.
icloud-reminders-mcp CLAUDE.md
Claude Code instructions for Lingnik/icloud-reminders-mcp, covering icloud-reminders-mcp — project conventions, backlog: github issues, always, secrets, architecture and testing.