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/sifxprime/kodelyth-ecc/code-reviewgit clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/code-review)<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/code-review"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/code-review.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.00022 | $0.02080 |
| Opus 5 | $0.00011 | $0.01040 |
| Sonnet 5 | $0.00004 | $0.00416 |
| Haiku 4.5 | $0.00002 | $0.00208 |
Grade A, and why
code-review 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 yesterday.
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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
PR review mode adapted from PRPs-agentic-eng by Wirasm. Part of the PRP workflow series.
Input: $ARGUMENTS
Mode Selection
If $ARGUMENTS contains a PR number, PR URL, or --pr:
→ Jump to PR Review Mode below.
Otherwise: → Use Local Review Mode.
Local Review Mode
Comprehensive security and quality review of uncommitted changes.
Phase 1 — GATHER
git diff --name-only HEAD
If no changed files, stop: "Nothing to review."
Phase 2 — REVIEW
Read each changed file in full. Check for:
Security Issues (CRITICAL):
- Hardcoded credentials, API keys, tokens
- SQL injection vulnerabilities
- XSS vulnerabilities
- Missing input validation
- Insecure dependencies
- Path traversal risks
Code Quality (HIGH):
- Functions > 50 lines
- Files > 800 lines
- Nesting depth > 4 levels
- Missing error handling
- console.log statements
- TODO/FIXME comments
- Missing JSDoc for public APIs
Best Practices (MEDIUM):
- Mutation patterns (use immutable instead)
- Emoji usage in code/comments
- Missing tests for new code
- Accessibility issues (a11y)
Phase 3 — REPORT
Generate report with:
- Severity: CRITICAL, HIGH, MEDIUM, LOW
- File location and line numbers
- Issue description
- Suggested fix
Block commit if CRITICAL or HIGH issues found. Never approve code with security vulnerabilities.
PR Review Mode
Comprehensive GitHub PR review — fetches diff, reads full files, runs validation, posts review.
Phase 1 — FETCH
Parse input to determine PR:
| Input | Action |
|---|---|
Number (e.g. 42) |
Use as PR number |
URL (github.com/.../pull/42) |
Extract PR number |
| Branch name | Find PR via gh pr list --head <branch> |
gh pr view <NUMBER> --json number,title,body,author,baseRefName,headRefName,changedFiles,additions,deletions
gh pr diff <NUMBER>
If PR not found, stop with error. Store PR metadata for later phases.
Phase 2 — CONTEXT
Build review context:
- Project rules — Read
CLAUDE.md,.claude/docs/, and any contributing guidelines - PRP artifacts — Check
.claude/PRPs/reports/and.claude/PRPs/plans/for implementation context related to this PR - PR intent — Parse PR description for goals, linked issues, test plans
- Changed files — List all modified files and categorize by type (source, test, config, docs)
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.
- yesterday First seen · 290 lines · 22 tokens per session scan A 35a81c54107b
code-review is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 2,080 once invoked, about $0.0001 per session on Opus 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-09-03.
Other commands, from other repositories
toh-help
Display all Toh Framework commands and quick usage guide.
opsx-new
Start a new change using the experimental artifact workflow (OPSX).
research
Delegate a thorough research investigation to the agy:runner subagent.
experiment
Design A/B test with statistical rigor. Usage: /mindforge:experiment [feature] [--metric conversion|engagement|revenue] [--duration 2w].
kimi-setup
Run node "$HOME/.kimi-plugin/kimi-companion.mjs" setup, then report installation and authentication status.
Obad
Search for given words or phrases in the book of Obadiah in one or multiple bibles.