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-frontend-navigation-with-react-routergit clone --depth 1 https://github.com/PackmindHub/packmindWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/packmindhub/packmind/packmind-frontend-navigation-with-react-router)<a href="https://agentmods.dev/instructions/packmindhub/packmind/packmind-frontend-navigation-with-react-router"><img src="https://agentmods.dev/badge/instructions/packmindhub/packmind/packmind-frontend-navigation-with-react-router.svg" alt="Measured on agentmods" height="20"></a>What 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.00229 | $0.00229 |
| Opus 5 | $0.00114 | $0.00114 |
| Sonnet 5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
packmind packmind-frontend-navigation-with-react-router.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 4d 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: Frontend Navigation with React Router
This codebase uses React Router v7 with organization and space scoping in URLs (e.g., /org/{orgSlug}/space/{spaceSlug}/recipes). To maintain consistency, improve maintainability, and simplify navigati... :
- Omit orgSlug and spaceSlug parameters to use current organization and space context by default and only specify them explicitly when navigating to a different organization or space.
- Use authentication route methods (routes.auth.*) for authentication-related navigation.
- Use organization-scoped route methods (routes.org.*) for pages that require only organization context.
- Use space-scoped route methods (routes.space.*) for pages that require both organization and space context.
- Use the routes utility from shared/utils/routes for all declarative navigation with Link and NavLink components.
- Use the useNavigation() hook from shared/hooks/useNavigation for all programmatic navigation with navigate().
Full standard is available here for further request: Frontend Navigation with React Router
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.
- 4d ago First seen · 14 lines · 229 tokens per session scan A 135f9deedf16
packmind packmind-frontend-navigation-with-react-router.instructions.md is an instructions file published in the GitHub repository PackmindHub/packmind (308 stars, last pushed today), licensed Apache-2.0. It adds 229 tokens to every session, about $0.0011 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.
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge architecture-principles.instructions.md
Core architecture principles — Architecture-First Approach, Separation of Concerns, TDD, Best Practices over Quick Wins. READ BEFORE any code changes.
plan-forge copilot-instructions.md
Copilot instructions for srnichols/plan-forge, covering instructions for copilot, architecture principles, core principles (non-negotiable), cost estimates and talking to forge-master.
plan-forge testing.instructions.md
Testing rules for Plan Forge — vitest patterns, fake-timers vs tolerance, mocking conventions, and how to read test output without hallucinating failures. Auto-loads when editing test files.