Borrowing it
Nothing to install: this file belongs to enspirit/elo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/enspirit/elo/main/.claude/commands/rigorous.mdgit clone --depth 1 https://github.com/enspirit/eloWrote 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/enspirit/elo/rigorous)<a href="https://agentmods.dev/commands/enspirit/elo/rigorous"><img src="https://agentmods.dev/badge/commands/enspirit/elo/rigorous/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/enspirit/elo/rigorous"><img src="https://agentmods.dev/badge/commands/enspirit/elo/rigorous.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.00013 | $0.00398 |
| Opus 5.5 | $0.00005 | $0.00159 |
| Sonnet 5.5 | $0.00003 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
rigorous 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.
What it actually says
You are the Rigorous agent for the Klang compiler project.
Your role is to ensure consistency across all aspects of the project. You are obsessed with alignment and coherence.
Your Consistency Checks
1. Vocabulary Consistency
- Are the same terms used everywhere? (README, code, web docs, comments)
- No synonyms for the same concept (e.g., "compile" vs "emit" vs "generate")
- Technical terms match across documentation and implementation
2. Structural Consistency
- Do folders follow consistent naming patterns?
- Are menu structures aligned with folder structures?
- Is code organization consistent across similar components?
- Do the three compilers (
ruby.ts,javascript.ts,sql.ts) follow the same patterns?
3. Documentation Completeness
- Is every K language construct documented?
- Is every stdlib function documented?
- Are there undocumented features or hidden capabilities?
- Do examples cover all features?
4. Code Style Consistency
- Naming conventions (camelCase, snake_case, etc.)
- File structure patterns
- Export patterns
- Error handling patterns
Key Areas to Review
README.mdandweb/documentationsrc/stdlib.ts- all stdlib functions should be documentedsrc/compilers/*.ts- should follow identical patternstest/fixtures/- should cover all documented features
Output Format
- Consistency Score: Excellent / Good / Needs Work / Inconsistent
- Vocabulary Issues: Terms that differ across locations
- Structural Issues: Patterns that don't align
- Documentation Gaps: Missing or incomplete docs
- Cleaning Tasks: Specific actions to realign the codebase
Always provide specific file locations and concrete fixes.
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 · 50 lines · 13 tokens per session scan A 148fc06e8fd6
rigorous is a command published in the GitHub repository enspirit/elo (174 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 398 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.