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/loggit 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/log)<a href="https://agentmods.dev/commands/janhesters/react-router-saas-template/log"><img src="https://agentmods.dev/badge/commands/janhesters/react-router-saas-template/log.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.00396 |
| Opus 5 | $0.00000 | $0.00198 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
log 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 5d 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
log
Act as a senior software engineer to log completed epics using the following template:
## $date
- $emoji - $epicName - $briefDescription
What to Log
LOG ONLY COMPLETED EPICS - Focus on completed epics that represent significant user-facing value:
- ✅ Epic Completions: Major feature releases, tool creation, system implementations
- ✅ User-Impacting Changes: New capabilities, workflows, or developer experience improvements
- ✅ Architecture Decisions: Significant refactoring, new patterns, or system redesigns
DO NOT LOG:
- ❌ Config file changes (.json, .config updates)
- ❌ File organization/moves (directory restructuring)
- ❌ Minor bug fixes (unless epic-level)
- ❌ Documentation updates (unless epic-level)
- ❌ Dependency updates
- ❌ Internal refactoring
- ❌ Test additions/changes
- ❌ Meta-work (logging, planning, etc.)
Emojis
Use the following emoji to represent the epic type:
- 🚀 - new feature
- 🐛 - bug fix
- 📝 - documentation
- 🔄 - refactor
- 📦 - dependency update
- 🎨 - design
- 📱 - UI/UX
- 📊 - analytics
- 🔒 - security
Constraints { Always use reverse chronological order. Add most recent epics to the top. Keep descriptions brief (< 50 chars). Focus on epic-level accomplishments, not implementation details. Never log meta-work or trivial changes. Omit the "epic" from the description. }
gitChanges() { git add . git --no-pager diff --cached }
planChanges() { Check the plan diff to detect recently completed plan tasks. }
detectChanges() { gitChanges |> planChanges |> logDetectedChanges }
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.
- 5d ago First seen · 65 lines · 0 tokens per session scan A 049eb024c203
log is a command published in the GitHub repository janhesters/react-router-saas-template (48 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 396 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.
ai-update
Update all CLAUDE.md files across the monorepo to reflect the current state of the codebase.
build
Smart build with validation, error detection, and auto-fix.
pre-commit-full
Command: /pre-commit-full Purpose: Comprehensive pre-commit validation orchestrating all error prevention checks.
scan-errors
Command: /scan-errors Purpose: Pattern-based error detection across the entire codebase with bulk auto-fix capabilities.
feature
Command "feature" from databayt/hogwarts, covering feature development command, usage, basic usage, with detailed requirements and with specific technical constraints.