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/packmindhub/packmind/packmind-rest-api-endpoint-designgit clone --depth 1 https://github.com/PackmindHub/packmindWhat 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.00157 | $0.00157 |
| Opus 5 | $0.00078 | $0.00078 |
| Sonnet 5 | $0.00031 | $0.00031 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
packmind packmind-rest-api-endpoint-design.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 3d 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
Standard: REST API Endpoint Design
Conventions for designing REST API endpoints that are predictable, self-documenting, and aligned with distinct business actions. Favors dedicated action endpoints over generic status updates, and rout... :
- Create one endpoint per business action rather than a single endpoint handling multiple actions via request body
- Only include resource IDs from the ownership chain in the route — omit IDs of related but non-parent resources
- Use dedicated POST action endpoints (e.g.,
/reject,/accept) instead of a generic PATCH with a status field in the body
Full standard is available here for further request: REST API Endpoint Design
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.
- 3d ago First seen · 11 lines · 157 tokens per session scan A ea5a957bcce0
packmind packmind-rest-api-endpoint-design.instructions.md is an instructions file published in the GitHub repository PackmindHub/packmind (306 stars, last pushed 5d ago), licensed Apache-2.0. It adds 157 tokens to every session, about $0.0008 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
token-saver CLAUDE.md
Instructions for ppgranger/token-saver, covering token-saver plugin, how it works and important rules.
arai CLAUDE.md
Instructions for taniwhaai/arai, covering claude.md — arai, commands, architecture, prompt-collector module (src/promptcollector.rs) and extending the match pipeline.
ai-agent-instruction-modules AGENTS.md
Instructions for tablackburn/ai-agent-instruction-modules, covering ai agent instructions, instructions for ai agents, instruction applicability matrix, available instruction files and quick reference.
arai AGENTS.md
Instructions for taniwhaai/arai, covering agents.md — arai, core discipline (non-negotiable), taniwha / subagent rules, work style and tool usage.
stenographer-mode copilot-instructions.md
Instructions for AkashAi7/stenographer-mode, covering steno mode — global instructions, contract, rules and levels.
booklib AGENTS.md
Instructions for booklib-ai/booklib, covering booklib, stack, key directories, commands and rules.