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 skills add kensaurus/cursor-kenji --skill iterate-post-launchgit 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/skills/kensaurus/cursor-kenji/iterate-post-launch)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/iterate-post-launch"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/iterate-post-launch/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/skills/kensaurus/cursor-kenji/iterate-post-launch"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/iterate-post-launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 57 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium MCP Rug Pull · line 135 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00069 | $0.02237 |
| Opus 5 | $0.00034 | $0.01118 |
| Sonnet 5 | $0.00014 | $0.00447 |
| Haiku 4.5 | $0.00007 | $0.00224 |
Grade A, and why
iterate-post-launch 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.
How it starts
The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iterate-post-launch — Production Signal → Prioritised Fix Loop
Degree of freedom: MIXED. Triage and sprint plan [HIGH freedom];
signal pulls, confirmation-before-edit, and live verify
[LOW freedom — run exactly].
You shipped. That is the beginning, not the end. Real users hit real paths you did not test. Sentry, Supabase logs, and the live UI tell you exactly what to fix next — if you know how to read them. This skill turns those signals into a ranked, actionable improvement plan and then implements it.
Plan → Signal → Triage → Fix → Verify. Do not guess what to improve. Let production data point to the highest-impact work first.
Before ANY browser action, read protocol-browser-anti-stall.
How to reason
- Observe — Sentry, Supabase logs/advisors, and a headed walkthrough in parallel
- Interpret — impact × effort from those signals, not a guessed redesign
- Classify — Critical / High / Medium / Low; present the sprint before editing
- Verify — live Playwright (or the failing query) before resolving the Sentry issue
Worked example
Observe: Sentry
TypeErroron/checkout2.4k events / 14d; advisor missing index onorders(user_id); live empty cart has no message. Interpret: checkout crash blocks paying users — outranks the index and the empty state. Classify: Critical = crash fix; High = index; Medium = empty-cart copy. Present that sprint; do not start a homepage rewrite. Verify: headed-s=post-launchreplay of checkout → 2xx; thensentry:update_issueresolved.
Self-critique before reporting
- Signal-backed — every fix traces to Sentry, logs, advisors, or the walkthrough
- Live before resolve — Playwright or the query, then Sentry resolved
- Rows ask first — asked-for schema ships; DELETE/UPDATE on real rows waits
- Right owner — one named bug →
workflow-fix-and-ship
Phase 0: Context [LOW freedom — run exactly]
Read the stack before pulling any signals:
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 · 282 lines · 69 tokens per session scan A c0427b0d2c75
iterate-post-launch is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 11d ago), licensed MIT. It adds 69 tokens to every session and 2,237 once invoked, about $0.0003 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 skills, from other repositories
debugging
Runs a hypothesis-driven debugging loop across any language or binary, escalating to orthogonal oracle angles and locking the fix with a failing test. Use for crashes, silent failures, hangs, wrong responses, memory leaks, async misbehavior, or reverse engineering.
lcx-report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.
ast-grep
Searches and rewrites code by AST shape across 25 languages. Use when the target is a syntax pattern (every call/class/import shaped like X, a codemod, a YAML rule) rather than literal text; for plain strings, comments, or filenames, use rg.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
lcx-doctor
Diagnose LazyCodex and Codex CLI installation health against the latest sources. Use whenever the user asks for a doctor or health check, says LazyCodex, lazycodex-ai, omo-codex, or Codex behaves oddly after an install, update, or config change, suspects a stale, drifted, or broken setup, or wants the local install…
firebase-crashlytics
Use when implementing crash reporting, capturing fatal/non-fatal errors, recording isolate/async exceptions, customizing reports, or uploading obfuscated symbols.