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.
git 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/plugins/blakecyze/kanso/kanso)<a href="https://agentmods.dev/plugins/blakecyze/kanso/kanso"><img src="https://agentmods.dev/badge/plugins/blakecyze/kanso/kanso/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/plugins/blakecyze/kanso/kanso"><img src="https://agentmods.dev/badge/plugins/blakecyze/kanso/kanso.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
kanso 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 1mo 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
{
"name": "kanso",
"version": "0.6.0",
"description": "Claude Code skills that keep AI-written code short and honest. Delete before you add, earn every line.",
"author": {
"name": "Blake Cyze",
"url": "https://cyze.dev"
},
"homepage": "https://github.com/blakecyze/kanso",
"repository": "https://github.com/blakecyze/kanso",
"license": "MIT",
"keywords": [
"claude-code",
"skills",
"code-quality",
"anti-slop",
"refactor",
"code-review",
"maintainability"
]
}
What it installs
The manifest is a name and a version. 11 skills, 1 hook travel with it, and installing the plugin installs all of them — 611 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill kanso-audit A 60 tokens
- Skill kanso-context A 58 tokens
- Skill kanso-nuclear A 60 tokens
- Skill kanso-refactor A 55 tokens
- Skill kanso-task A 45 tokens
- Skill kanso-commit A 31 tokens
- Skill kanso-council A 90 tokens
- Skill kanso-pr A 32 tokens
- Skill kanso-handoff A 86 tokens
- Skill kanso-prompting A 51 tokens
- Skill kanso-principles A 43 tokens
- Hook PostToolUse A not measured
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed 2b8651bfd311
- 1mo ago First seen · 22 lines scan A 44ded9a66b0f
kanso is a plugin published in the GitHub repository blakecyze/kanso (4 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
zuvo
Multi-agent skill ecosystem for structured software development. 58 skills and 26 specialized agents with quality gates, code exploration, and evidence-based review.
development-skills
Use for coding, debugging, refactoring, design, test strategy, code review, documentation alignment, and development research. A language-agnostic direct, bounded, or full workflow with persistent decisions and independent review.
dotnet-backend
Pure .NET 10 backend architecture for Kestrel-hosted REST and SignalR services with DI, data access, and SOLID review.
dead-code
Find and remove dead code, unused imports, and duplicates across any language.
esp32-cpp
ESP32 firmware review for all variants, FreeRTOS, ESP-IDF/PlatformIO, peripherals, and memory.
python-backend
Python backend architecture for Litestar and FastAPI with SQLAlchemy and SOLID patterns.