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/thought2code/mcp-java-sdk-examples/agents-mdgit clone --depth 1 https://github.com/thought2code/mcp-java-sdk-examplesWhat 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.00141 | $0.00141 |
| Opus 5 | $0.00071 | $0.00071 |
| Sonnet 5 | $0.00028 | $0.00028 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
mcp-java-sdk-examples 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- mcp-annotated-java-sdk AGENTS.md — 100% identical, 0 lines differ
What it actually says
Git Commit Rules
When committing code, you MUST follow these rules:
Commit message format
Use Conventional Commits:
<type>(<scope>): <subject>
Allowed types:
- feat
- fix
- docs
- style
- refactor
- perf
- test
- build
- ci
- chore
Examples:
feat(auth): add oauth login support
fix(order): prevent duplicate payment processing
Rules:
- subject must be lowercase
- subject max length 72 chars
- no period at the end
- use imperative mood
- commit message must be written in English
Before committing:
- run git diff --cached
- verify commit message format
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 · 42 lines · 141 tokens per session scan A f6e6118d5e29
mcp-java-sdk-examples AGENTS.md is an instructions file published in the GitHub repository thought2code/mcp-java-sdk-examples (33 stars, last pushed 6d ago), licensed MIT. It adds 141 tokens to every session, about $0.0007 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
demo-game CLAUDE.md
Instructions for mcp-gtw/demo-game, covering claude.md, what this is, layout (src/app/), client (client/, built with vite) and game rules and where each one lives.
llm-context.py CLAUDE.md
Instructions for cyberchitta/llm-context.py, covering claude.md, working notes (gitignored) and draining the field notes.
openrouter-mcp-multimodal AGENTS.md
Instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
seekstone CLAUDE.md
Instructions for shaqmughal/seekstone, covering claude.md, what this repo is, commands, the harness itself (run after npm install) and architecture.
Plonk AGENTS.md
Instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
mcp-dockhand copilot-review.instructions.md
Instructions for strausmann/mcp-dockhand: When reviewing pull requests in this repository.