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 audit-skill-conflictsgit 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/audit-skill-conflicts)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/audit-skill-conflicts"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-skill-conflicts.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.00074 | $0.01868 |
| Opus 5 | $0.00037 | $0.00934 |
| Sonnet 5 | $0.00015 | $0.00374 |
| Haiku 4.5 | $0.00007 | $0.00187 |
Grade A, and why
audit-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 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
audit-skill-conflicts — Pack coherence, not product QA
Degree of freedom: MIXED — Phases 0–1 [HIGH freedom]; Phase 2 routing
dry-run [LOW freedom] — skip explicitly if the harness cannot show
selection. Never write audit-responsive-layout.
Read-only. Most other audit-* skills inspect an app or repository you
ship. This one inspects the skill pack it lives in.
npm run validate:skills checks each file in isolation (name = dir, description
≤320, body <500). It cannot see two skills giving opposite advice, six
descriptions all matching "audit my UI", a handoff to a renamed skill, or a
greedy description that fires constantly and burns context.
A skill collection is a system. Its failure modes are between files.
Present findings. Rewrite nothing until approved. Highest-leverage first: description rewrites (routing) — they change which skill fires without changing any skill's behavior.
This skill vs neighbors
| Skill | Owns |
|---|---|
| audit-skill-conflicts (this) | Cross-skill contradictions, routing, dangling refs, bloat |
meta-skill-creator |
How to write a SKILL.md |
validate:skills (script) |
Per-file spec lint — not semantic coherence |
enhance-agent-guardrails |
Guardrails in an app repo, not this pack |
plan-docs-sync |
Docs vs code drift — not skill vs skill |
Do not fire for "create a skill" → meta-skill-creator.
Do not fire for "audit my app's UI" → audit-ux / audit-responsive /
audit-ui-states (this skill would flag that cluster).
How to reason
- Observe — quote both descriptions (or rule vs skill) that appear to collide
- Interpret — can one user phrase honor both, or do they contradict / steal routing?
- Classify — contradiction / trigger overlap / stale ref / bloat / correct carve-out
- Severity — opposite stance on the same situation, or a greedy description, first
Worked example
Observe: "audit my UI" matches
audit-ux,audit-responsive,audit-ui-stateswith no carve-out in two of the three descriptions. Interpret: the agent cannot know whether to score heuristics, breakpoints, or empty states. Classify: trigger overlap without disambiguation. Severity: major — wrong skill fires; wasted context. Fix: each description names when it wins (layout vs heuristics vs states).
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 · 174 lines · 74 tokens per session scan A c2b190101730
audit-skill-conflicts is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 10d ago), licensed MIT. It adds 74 tokens to every session and 1,868 once invoked, about $0.0004 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
comprehensive-enrichment
Enrich any person or company from any identifier — email, name, LinkedIn URL, domain, company name, Twitter/X handle. Use when asked to enrich, look up, or research a lead, contact, person, or company.
paid-channel-prioritizer
For founders who don't know where to start with paid ads. Analyzes ICP, competitor ad presence, budget constraints, and product type to recommend which 1-2 paid channels to start with and provides a 90-day ramp plan. Prevents the common mistake of spreading a small budget across too many platforms.
data-charts-tako
Search and visualize the world's data - get charts, insights, and embeddable knowledge cards for finance, economics, demographics, sports, and more.
email-finder-hunter
Email finder and verifier - find emails, verify deliverability, discover companies.
lead-discovery
Orchestrator that runs first for lead generation requests. Gathers business context via website analysis or questions, identifies competitors, builds ICP, and routes to signal skills with pre-filled inputs.
render-mosaic-grid-reveal
Render a 'mosaic-grid-reveal' video from a config — a real-DOM FULL-BLEED N×N mosaic of real product tiles that pops in one tile at a time (scatter order, ease-out-back overshoot), the grid clears, then the brand wordmark builds line-by-line followed by a sub-label, tagline, and CTA; frame-stepped via Playwright and…