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 blakecyze/kanso --skill kanso-auditgit clone --depth 1 https://github.com/blakecyze/kansoWrote 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/blakecyze/kanso/kanso-audit)<a href="https://agentmods.dev/skills/blakecyze/kanso/kanso-audit"><img src="https://agentmods.dev/badge/skills/blakecyze/kanso/kanso-audit/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/blakecyze/kanso/kanso-audit"><img src="https://agentmods.dev/badge/skills/blakecyze/kanso/kanso-audit.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.04008 |
| Opus 5 | $0.00030 | $0.02004 |
| Sonnet 5 | $0.00012 | $0.00802 |
| Haiku 4.5 | $0.00006 | $0.00401 |
Grade A, and why
kanso-audit 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 12d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kanso-audit
Code review that reports findings, proposes concrete fixes, and — on approval — either hands cleanup off to /kanso-refactor or applies the fix in place. The principles from kanso-principles govern both the findings and the fixes.
Four phases:
- Phase A — Investigation. Read-only. Gather context and produce the findings report using the framework below. The skill's
allowed-toolsdeliberately exclude Edit/Write so the investigation cannot modify files. - Phase B — Proposal. Translate Tier 1 and Tier 2 findings into a numbered list. Tag each entry by shape:
refactor(behaviour-preserving) orbehaviour-change(correctness, security, architecture). Show the list in the approval block and wait. - Phase C — Apply.
- For
refactor-shaped fixes → hand off to/kanso-refactor audit-report. That skill already enforces the behaviour-preserving rule, has the refactor taxonomy, and knows how to split work into commit-able groups. Don't reimplement it here. - For
behaviour-changefixes → apply in place in the main session, one at a time, re-reading each file immediately before editing. These are not refactors; each is a real behaviour change and the user has approved it as such.
- For
- Phase D — Verify. Run the project's verification command after fixes land. Paste the exit code. If no command exists, say so plainly — don't claim success without evidence.
Always run inline
This skill runs in the calling chat. Never dispatch the audit via the Agent or Task tool, never delegate it to a subagent, never hand it off to a parallel runner. The findings, the approval gate, and any follow-up /kanso-refactor invocation all happen in the user's current transcript so the user can see and act on them directly. A subagent run produces output in a side window the user can't easily reach — that defeats the point.
Same rule for the follow-up: when /kanso-refactor is invoked from the approval gate, it runs inline too.
Exception: --fresh for Phase A only
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.
- 12d ago First seen · 261 lines · 60 tokens per session scan A 70af71e80ae9
kanso-audit is a skill published in the GitHub repository blakecyze/kanso (3 stars, last pushed 8d ago), licensed MIT. It adds 60 tokens to every session and 4,008 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-08-31.
Other skills, from other repositories
code-reviewer
Code review knowledge base: quality, security (OWASP Top 10), error-handling, performance, and test-coverage checklists with severity-ranked output format. Use when reviewing code changes, PRs, or before commits. Loaded automatically by the code-reviewer agent.
mutation-test
Mutation testing with two engines. Uses the project's NATIVE mutation runner (StrykerJS / Infection / mutmut / PIT / cargo-mutants) when one is configured — installing it on explicit consent when it is not — for a reproducible, comparable score; and an LLM-guided engine for the mutation classes native mutators cannot…
review
Structured code review with parallel audit agents, confidence-scored triage, and optional auto-fix. Examines uncommitted changes, staged diffs, commit ranges, or specific paths. Produces a tiered report (MUST-FIX / RECOMMENDED / NIT) backed by evidence, then optionally applies fixes with verification.
db-audit
Database performance and safety audit. 70+ checks across 13 dimensions (DB1-DB13): query patterns, indexes, schema design, connections, transactions, migrations, caching, query optimization, ORM anti-patterns, observability, data lifecycle, DB security, and migration deployment safety. Code-level checks for all ORMs.…
write-tests
Write tests for existing production code. Processes ONE file at a time through a full pipeline: analyze, inventory (frozen BEFORE writing), write, executable coverage gate, verify, blind coverage audit, adversarial review, log. Uses CodeSift for discovery and analysis when available. Modes: [path] (specific target)…
brainstorm
Explores a codebase, researches the problem space, and produces an approved design specification before any code is written. Use when the user wants to create a new feature, add significant functionality, redesign a subsystem, or build something that touches multiple parts of the project.