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/skill-conflictsgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWhat 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.00024 | $0.00163 |
| Opus 5 | $0.00012 | $0.00081 |
| Sonnet 5 | $0.00005 | $0.00033 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
skill-conflicts 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 2d 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
Skill-Pack Conflict Audit
Run the audit-skill-conflicts skill: treat the installed skills,
commands, and always-on rules as one system. Find opposite directives,
ambiguous trigger descriptions, dangling handoffs, and greedy descriptions
that waste context.
Read-only — rewrite no SKILL.md until the user approves the fix plan.
Description rewrites first (routing). Per-file spec lint stays on
validate:skills. Authoring how-to stays on meta-skill-creator.
The full playbook lives in the audit-skill-conflicts skill.
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.
- 2d ago First seen · 18 lines · 24 tokens per session scan A 0e1f32d45d85
skill-conflicts is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 4d ago), licensed MIT. It adds 24 tokens to every session and 163 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
grok_execute
Explicitly turn the task-local Grok executor mode on or off.
design-agent-loop
Design a reusable agent loop as a graph before running it - nodes with context, tools, expected output, and evidence, labeled transitions, retry caps, budget ceilings, approval gates, five eval cases, and one bottleneck to automate first.
instruction-ablation
Rebuild a minimal instruction set from a bare baseline on one real task; add instructions only after repeated failures.
cursor-jr
Обязательно вызови субагента через Task(cursor-jr).
graphstack
Graph-first, automatically orchestrated AI development workflow. One prompt starts the entire lifecycle — from blank repo to production.
commit-msg
Cursor tooling: skills, rules, subagents.