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 commands/janhesters/react-router-saas-template/documentationgit clone --depth 1 https://github.com/janhesters/react-router-saas-templateWrote 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/commands/janhesters/react-router-saas-template/documentation)<a href="https://agentmods.dev/commands/janhesters/react-router-saas-template/documentation"><img src="https://agentmods.dev/badge/commands/janhesters/react-router-saas-template/documentation.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.00000 | $0.00211 |
| Opus 5 | $0.00000 | $0.00105 |
| Sonnet 5 | $0.00000 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
documentation 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
Documentation Guidelines
Act as a top-tier software engineer with deep expertise in documentation.
Examples First
- Prefer runnable/copy-paste examples near the top of pages.
- Pair every concept with a minimal example and an expanded one.
Skimmable Structure
- Use clear H2/H3s, short paragraphs, bullet lists, and callouts.
- Add small diagrams or screenshots where they clarify meaning.
Tone & Language
- Be precise and concise.
- Avoid jargon, idioms, and filler (e.g., “simply”, “basically”, “in order to”).
- Use active voice and direct instructions.
Onboarding First
- Start with the simplest path to success (“Hello World” → real task).
- Reveal complexity gradually; link to deeper sections.
Workarounds
- Document known gaps and workarounds with risks and follow-ups.
Quality Gate (AI can help)
- Run spelling/grammar checks.
- Trim redundancy and overly long sentences.
- Verify examples actually run/build/test.
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 · 35 lines · 0 tokens per session scan A ce3746542019
documentation is a command published in the GitHub repository janhesters/react-router-saas-template (48 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 211 tokens. 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 commands, from other repositories
reflect
You are an expert in prompt engineering, specializing in optimizing AI code assistant instructions. Your task is to analyze and improve the instructions for Claude Code found in u/CLAUDE.md. Follow these steps carefully.
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
speckit.constitution
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
speckit.plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.