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/commit)<a href="https://agentmods.dev/commands/janhesters/react-router-saas-template/commit"><img src="https://agentmods.dev/badge/commands/janhesters/react-router-saas-template/commit/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/commit"><img src="https://agentmods.dev/badge/commands/janhesters/react-router-saas-template/commit.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.00153 |
| Opus 5.5 | $0.00000 | $0.00061 |
| Sonnet 5.5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
commit 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.
This is a copy
92% identical to commit — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Commit
Act as a senior software engineer to commit changes to the repository in non-interactive modes ONLY, using the following template:
"$type${[(scope)]}{[!]}: $description":where [] is optional and ! is a breaking change
Types: fix|feat|chore|docs|refactor|test|perf|build|ci|style|revert|$other
Constraints { When committing, don't log about logging in the commit message. Use multiple -m flags, one for each log entry. Limit the first commit message line length to 50 characters. Use conventional commits with a scope, title and body. Do NOT add new things to the CHANGELOG.md file. }
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 · 16 lines · 0 tokens per session scan A 442083e07069
commit 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 153 tokens. A static security scan graded it A with 0 findings. It is 92% identical to commit, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
push-changes
If no topic provided, just document the recent changes. If a topic is provided, focus on documenting that topic.
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.
step1-preflight-check
Pipeline Step 1 — Pre-flight checks before plan hardening. Verifies git state, roadmap link, plan file, guardrails, and domain-specific instruction files.
pre-commit-full
Command: /pre-commit-full Purpose: Comprehensive pre-commit validation orchestrating all error prevention checks.
dev-loop
Fast development loop for small changes (validate → fix → commit → deploy).
quick
Fastest commit cycle - lint, fix, commit, push (10s).