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/apache/pulsar/java-codinggit clone --depth 1 https://github.com/apache/pulsarWhat 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.00086 | $0.00086 |
| Opus 5 | $0.00043 | $0.00043 |
| Sonnet 5 | $0.00017 | $0.00017 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
pulsar java-coding.instructions.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
Java code changes
Apache Pulsar is performance-critical, asynchronous, and concurrency-sensitive. The full reference is
CODING.md (with CONTRIBUTING.md for running tests) —
follow it when editing or reviewing Java code.
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 · 10 lines · 86 tokens per session scan A 4850e94bf3ad
pulsar java-coding.instructions.md is an instructions file published in the GitHub repository apache/pulsar (15,319 stars, last pushed 3d ago), licensed Apache-2.0. It adds 86 tokens to every session, about $0.0004 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
rocketmq-rust AGENTS.md
Instructions for mxsm/rocketmq-rust, covering agents.md, scope and precedence, repository boundaries, working agreement and rust engineering guardrails.
baguette CLAUDE.md
Instructions for tddworks/baguette, covering claude.md, tdd is non-negotiable (read this first), naming the abstractions, splitting an adapter that wraps 3rd-party i/o and coverage target.
baguette AGENTS.md
Instructions for tddworks/baguette, covering agents.md, tdd is non-negotiable (read this first), naming the abstractions, splitting an adapter that wraps 3rd-party i/o and coverage target.
nuclear AGENTS.md
AGENTS.md instructions for nukeop/nuclear, covering agents.md, project overview, packages, commands and development.
nuclear copilot-instructions.md
Copilot instructions for nukeop/nuclear, covering nuclear music player - copilot instructions, project overview, key features, tech stack and packages.
rabbitmq-server AGENTS.md
AGENTS.md instructions for rabbitmq/rabbitmq-server, covering instructions for ai agents, website and github repositories, building and testing, dialyzer and xref and repository structure.