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/kensaurus/cursor-kenji/feedback-to-closuregit 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/feedback-to-closure)<a href="https://agentmods.dev/commands/kensaurus/cursor-kenji/feedback-to-closure"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/feedback-to-closure.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.00030 | $0.00393 |
| Opus 5 | $0.00015 | $0.00197 |
| Sonnet 5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
feedback-to-closure 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
Feedback → Closure
Turn raw feedback — bug reports, user complaints, review comments, Sentry issues, QA/audit findings — into deduplicated, durable, trackable tickets and drive each to production-verified closure.
Follow the workflow-feedback-to-closure skill end to end. In brief:
- Gather and normalize every signal with its source (reports, Sentry, QA, audits, review comments, logs).
- Dedupe and cluster — one defect = one ticket; search the tracker and
.cursor/state before creating anything; route feature requests and by-design items out. - Write reproducible tickets with repro, expected/actual, suspected area,
and observable acceptance; persist to
.cursor/feedback-closure-state.md(andgh issue createwhen a tracker is used). - Prioritize by impact × severity ÷ effort.
- Fix through the right skill —
workflow-fix-and-ship,complete-everything,debug-fe-be-integration, orworkflow-green-repo; add a regression test. - Verify and close only after the fix is confirmed where the user hit it; resolve linked Sentry/tracker issues. Closing before live verification is forbidden.
A ticket is closed only when verified in production — not when a PR merges.
The full playbook lives in the workflow-feedback-to-closure skill.
Related: workflow-fix-and-ship, iterate-post-launch,
workflow-ship-and-observe, debug-sentry-monitor.
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 · 36 lines · 30 tokens per session scan A fd14101e721f
feedback-to-closure is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 7d ago), licensed MIT. It adds 30 tokens to every session and 393 once invoked, about $0.0002 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
next-task
Intelligently determine and prepare the next action based on comprehensive context.
setup-models
Run interactive setup to configure AI models.
to-review
Command "to-review" from eyaltoledano/claude-task-master, covering marking task for review, when to use review status, execution and review preparation.
quick-install-taskmaster
Quick install Task Master globally if not already installed.
cursor-jr-sync
Запусти синхронизацию официальной документации Cursor.
cursor-jr
Обязательно вызови субагента через Task(cursor-jr).