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/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/green-repo)<a href="https://agentmods.dev/commands/kensaurus/cursor-kenji/green-repo"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/green-repo.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.1 | $0.00026 | $0.00418 |
| Opus 5 | $0.00013 | $0.00209 |
| Sonnet 5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
green-repo 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 8d 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
Green Repo
Drive the entire repository to a verified-green baseline: typecheck, lint,
tests, and build all passing from a clean run. Use this only when fixing
pre-existing debt is explicitly authorized — for a single plan use
/complete-everything, and for one searchable pattern use /burndown-full.
Follow the workflow-green-repo skill end to end. In brief:
- Confirm scope and discover gates — whole repo vs. a package. Read
package.json,Makefile, CI workflows, andAGENTS.md/CLAUDE.mdfor the real typecheck/lint/test/e2e/build commands. Capture the baseline. - Enumerate every failure into
.cursor/green-repo-state.md, separating real failures from flaky/environment-dependent ones. State the totals. - Fix root causes in batches, ticking each immediately. Never skip,
.only,@ts-ignore, or blanket-update snapshots to force green. Append newly surfaced failures and fix them in this run. - Prove green from scratch — re-run every gate clean; zero unchecked failures outside justified, human-signed-off exceptions.
- Report the result, fixed count, quarantined items, and any real environment blockers.
Green is defined by a fresh from-scratch run of every gate, not by the failures you happened to notice.
The full playbook lives in the workflow-green-repo skill.
Related: complete-everything (one plan's connected scope), burndown-full
(one searchable pattern), verification-before-completion (evidence levels),
completion-judge (independent green verdict).
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.
- 8d ago First seen · 36 lines · 26 tokens per session scan A ecd09795418f
green-repo is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 10d ago), licensed MIT. It adds 26 tokens to every session and 418 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-08-31.
Other commands, from other repositories
publish
Publish oh-my-opencode to npm via GitHub Actions workflow.
benchmark
Design and coordinate a reproducible Java performance test.
upload-report
Run automation and upload or verify Katalon Platform reports for Katalon Studio/KRE, JUnit XML, and Playwright reports. Use when you need to combine Katalon MCP project/result discovery with Katalon CLI execution, Katalon Report Uploader, or @katalon/playwright-reporter; configure report folders, report types…
plan-refactor
Plan a refactor as a sequence of safe verified steps, with tests established before anything moves.
prompt-optimization
Improve an underperforming prompt through structured changes measured against fixed cases.
verify-work
Execute a work item's testing-plan.md after implementation — run the planned activities, record results, commit the evidence (verification phase).