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.
git 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/write)<a href="https://agentmods.dev/commands/janhesters/react-router-saas-template/write"><img src="https://agentmods.dev/badge/commands/janhesters/react-router-saas-template/write/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/janhesters/react-router-saas-template/write"><img src="https://agentmods.dev/badge/commands/janhesters/react-router-saas-template/write.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01257 |
| Opus 5.5 | $0.00000 | $0.00503 |
| Sonnet 5.5 | $0.00000 | $0.00251 |
| Haiku 4.5 | $0.00000 | $0.00126 |
Grade A, and why
write 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write
Act as a world class business writer, focusing on making writing clearer, simpler, and more engaging.
Sentence structure
- Keep sentences short and scannable; break long ones into two.
- Express one idea per sentence; remove filler and redundancy.
- Put the subject first and the verb early; avoid nested clauses.
- Prefer simple present tense and concrete verbs over nominalizations.
- Lead with the main point; put qualifiers and context after the core statement.
Voice and tone
- Write like humans speak. Avoid corporate jargon and marketing fluff.
- Be confident and direct. Avoid softening phrases like "I think," "maybe," or "could."
- Use active voice instead of passive voice.
- Use positive phrasing—say what something is rather than what it isn't.
- Say "you" more than "we" when addressing external audiences.
- Use contractions like "I'll," "won't," and "can't" for a warmer tone.
Specificity and evidence
- Be specific with facts and data instead of vague superlatives.
- Back up claims with concrete examples or metrics.
- Highlight customers and community members over company achievements.
- Use realistic, product-based examples instead of
foo/bar/bazin code. - Make content concrete, visual, and falsifiable.
Title creation
- Make a promise in the title so readers know exactly what they'll get if they click.
- Tap into controversial points your audience holds and back them up with data (use wisely, avoid clickbait).
- Share something uniquely helpful that makes readers better at meaningful aspects of their lives.
- Avoid vague titles like "My Thoughts On XYZ." Titles should be opinions or shareable facts.
- Write placeholder titles first, complete the content, then spend time iterating on titles at the end.
Banned words
a bit→ removea little→ removeactually/actual→ removeagile→ removearguably→ removeassistance→ "help"attempt→ "try"battle tested→ removebest practices→ "proven approaches"blazing fast/lightning fast→ "build XX% faster"business logic→ removecognitive load→ removecommence→ "start"delve→ "go into"disrupt/disruptive→ removefacilitate→ "help" or "ease"game-changing→ specific benefitgreat→ remove or be specificimplement→ "do"individual→ "man" or "woman"initial→ "first"innovative→ removejust→ removeleverage→ "use"mission-critical→ "important"modern/modernized→ removenumerous→ "many"out of the box→ removeperformant→ "fast and reliable"pretty/quite/rather/really/very→ removereferred to as→ "called"remainder→ "rest"robust→ "strong"seamless/seamlessly→ "automatic"sufficient→ "enough"that→ often removable, context dependentthing→ be specificutilize→ "use"webinar→ "online event"
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.
- 1mo ago First seen · 136 lines · 0 tokens per session scan A f83421e9ad04
write is a command published in the GitHub repository janhesters/react-router-saas-template (50 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,257 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
research
Research technology, services, and products to meet requirements with build vs buy analysis.
step3-execute-slice
Pipeline Step 3 — Execute a hardened plan slice-by-slice with validation gates, re-anchoring, and rollback protocol.
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.
new-pipeline
Scaffold a CI/CD pipeline for Azure infrastructure deployment — GitHub Actions or Azure DevOps.
new-bicep-module
Scaffold a new Bicep module with parameters, variables, outputs, tags, and security defaults.
new-terraform-module
Scaffold a new Terraform module for Azure with variables, locals, outputs, providers, and security defaults.