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/bep/gitjoin/agents-mdgit clone --depth 1 https://github.com/bep/gitjoinWhat 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.00114 | $0.00114 |
| Opus 5 | $0.00057 | $0.00057 |
| Sonnet 5 | $0.00023 | $0.00023 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
gitjoin 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 yesterday.
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
- Brevity is good, don't be clever.
- When doing copy-edits, try to stay as close to the style of the origin as possible.
- Assume that the maintainers and readers of the code you write are Go experts:
- Don't use comments to explain the obvious.
- Use self-explanatory variable and function names.
- Use short variable names when the context is clear.
- Never export symbols that's not needed outside of the package.
- Avoid global state at (almost) all cost.
- Confirm by running
check.sh.
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.
- yesterday First seen · 9 lines · 114 tokens per session scan A 018a43bd3f0a
gitjoin AGENTS.md is an instructions file published in the GitHub repository bep/gitjoin (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 114 tokens to every session, about $0.0006 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
github-mcp-server copilot-instructions.md
Instructions for github/github-mcp-server, covering github mcp server - copilot instructions, project overview, critical build & validation steps, required commands (run before committing) and when modifying mcp tools/endpoints.
av CLAUDE.md
Instructions for aviator-co/av, covering claude.md, project overview, documentation sources, command structure philosophy and development workflow.
ghtkn AGENTS.md
Instructions for suzuki-shunsuke/ghtkn, a project described as: A CLI to create short-lived (8 hours) GitHub App User Access Token for secure local development.
vscode-gitlens CLAUDE.md
Claude Code instructions for gitkraken/vscode-gitlens, a project described as: Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via…
msaccess-vcs-addin AGENTS.md
AGENTS.md instructions for joyfullservice/msaccess-vcs-addin, covering project overview, repository structure, architecture overview, component diagram and key architectural patterns.
next-sanity-starter AGENTS.md
Instructions for backendforth/next-sanity-starter, covering agents.md — next-sanity-starter, tl;dr, principles (priority order — apply top-down when in doubt), repository map and the module pattern (the most important concept).