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/kbichave/skillsWrote 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/kbichave/skills/skills)<a href="https://agentmods.dev/plugins/kbichave/skills/skills"><img src="https://agentmods.dev/badge/plugins/kbichave/skills/skills/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/kbichave/skills/skills"><img src="https://agentmods.dev/badge/plugins/kbichave/skills/skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
deep 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 11d 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": "deep",
"description": "Discover, plan, and implement complex systems with AI-assisted research, multi-LLM review, TDD sections, and disciplined execution",
"version": "5.23.0",
"author": {
"name": "kbichave",
"url": "https://github.com/kbichave"
},
"repository": "https://github.com/kbichave/skills",
"license": "MIT",
"keywords": [
"planning",
"implementation",
"tdd",
"architecture",
"llm-review",
"execution",
"discovery",
"system-design",
"build-vs-buy"
]
}
What it installs
The manifest is a name and a version. 5 skills, 22 agents, 6 hooks travel with it, and installing the plugin installs all of them — 2,319 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill review-panel A 0 tokens
- Skill dq-investigate A 183 tokens
- Skill humanizer A 208 tokens
- Skill no-op-remover A 147 tokens
- Skill deep B 0 tokens
- Agent code-reviewer A 125 tokens
- Agent domain-context-reader A 129 tokens
- Agent dq-hypothesizer A 142 tokens
- Agent dq-prover A 155 tokens
- Agent model-context A 97 tokens
- Agent section-writer A 26 tokens
- Agent monitor-reviewer A 116 tokens
- Agent pep8-reviewer A 119 tokens
- Agent review-verifier A 61 tokens
- Agent skill-router A 50 tokens
- Agent vault-curator A 51 tokens
- Agent claim-verifier A 91 tokens
- Agent data-eng-reviewer A 82 tokens
- Agent opus-plan-reviewer A 17 tokens
- Agent audit-doc-writer A 26 tokens
- Agent prompt-reviewer A 92 tokens
- Agent skill-reviewer A 79 tokens
- Agent logic-reviewer A 53 tokens
- Agent ml-reviewer A 67 tokens
- Agent mlops-reviewer A 86 tokens
- Agent stats-reviewer A 67 tokens
- Agent architecture-reviewer A 50 tokens
- Hook PostToolUse A not measured
- Hook PreToolUse A not measured
- Hook SubagentStop A not measured
- Hook Stop A not measured
- Hook PreCompact A not measured
- Hook SessionStart 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.
- 11d ago Changed 37a978112518
- 17d ago Changed 42d6aa64a270
- 20d ago Changed e102142021ed
- 1mo ago Changed 3769c9a19daf
- 1mo ago Changed · +10 lines 79c443098fee
- 1mo ago First seen · 13 lines scan A 2fd5f97b9a91
deep is a plugin published in the GitHub repository kbichave/skills (2 stars, last pushed 11d 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
han-communication
Foundational communication plugin for the Han suite. Owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the readability-guidance skill that surfaces the first two into a calling skill's own context for in-voice…
han-research
Pre-planning knowledge-work skills for the Han suite: understanding a problem before anyone commits to a plan. Home of research (research an open-ended question and end at an adversarially-validated recommendation), gap-analysis (compare two artifacts and report what is missing, incomplete, or conflicting), and…
ci-review
CI-optimized code review: multi-agent parallel review with confidence scoring and atomic GitHub PR review posting via gh api.
pr-trains
Batch operators for GitHub queues: review-train reviews every open PR, fix-train applies requested changes, fix-ci-train turns red CI green, merge-train fixes and merges in dependency order, issue-train triages and builds one PR per actionable issue — all with parallel sub-agents and one grouped confirmation.
8-habit-ai-dev
Anti-Vibe-Coding plugin — 7-step workflow discipline + 8-Habit cross-verification for AI-assisted development.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.