Back to search
claude-toolbox
SkillWorks with Claude CodeGitHubIncomplete
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Checked today
Check it deeper on your machine
It has changed since its scan on 15 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/serpro69/claude-toolbox with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/serpro69/claude-toolbox'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/serpro69--claude-toolbox)HTML
<a href="/listings/serpro69--claude-toolbox"><img src="/api/listings/serpro69--claude-toolbox/badge.svg" alt="findsafeskills safety rating" /></a>Install
i
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 32 lines
- {
- "name": "claude-toolbox",
- "owner": {
- "name": "serpro69",
- "url": "github.com/serpro69"
- },
- "metadata": {
- "description": "Development workflows from claude-toolbox"
- },
- "plugins": [
- {
- "source": "./klaude-plugin",
- "name": "kk",
- "version": "0.25.4",
- "author": {
- "name": "serpro69",
- "url": "github.com/serpro69"
- },
- "homepage": "https://serpro69.github.io/claude-toolbox/",
- "repository": "https://github.com/serpro69/claude-toolbox",
- "license": "Apache-2.0",
- "description": "Development workflow skills, commands, and hooks",
- "keywords": [
- "development",
- "workflow",
- "code-review",
- "testing",
- "documentation"
- ]
- }
- ]
- }
README.md · README · 123 lines
- <div align="center">
- <picture>
- <source media="(prefers-color-scheme: dark)" srcset="docs/assets/images/lockup-dark.svg">
- <img src="docs/assets/images/lockup-light.svg" alt="claude-toolbox" width="720">
- </picture>
- </div>
- # claude-toolbox
- [](https://github.com/serpro69/claude-toolbox/releases)
- [](https://github.com/hesreallyhim/awesome-claude-code)
- [](https://serpro69.github.io/claude-toolbox/)
- <div align="center"
- <picture>
- <img width="1080" alt="Terminal view" src="https://github.com/user-attachments/assets/27ef7269-0153-47c0-b07d-ed6a9504a176" />
- </picture>
- </div>
- `claude-toolbox` is a collection of "tools" for all your agentic workflows — pre-configured MCP servers, skills, sub-agents, commands, hooks, statuslines with themes, and more - everything you need for AI-powered development workflows, used and battle-tested daily on many of my own projects.
- **Supported providers:** [Claude Code](https://serpro69.github.io/claude-toolbox/latest/providers/claude-code/) · [Codex](https://serpro69.github.io/claude-toolbox/latest/providers/codex/)
- <div align="center">
- ## [Read the full documentation →](https://serpro69.github.io/claude-toolbox/latest/)
- <a href="https://serpro69.github.io/claude-toolbox/latest/">
- <img width="1080" alt="Docs landing page" src="https://github.com/user-attachments/assets/f6af0017-7f78-476b-8399-81eda8673d0a" />
- </a>
- ### [Or explore how claude-toolbox was used in a real project →](https://serpro69.github.io/claude-toolbox/latest/explore/)
- <a href="https://serpro69.github.io/claude-toolbox/latest/explore/">
- <img width="1080" alt="Explore page" src="https://github.com/user-attachments/assets/1adbbaa6-579c-4f27-94b1-8515cfefc2ec" />
- </a>
- </div>
- ---
- > [!IMPORTANT]
- > This project was created with the help of Claude-Code. Is it, however, always reviewed, tested, and reworked with a human-in-the-loop.
- >
- > No AI slop here. Purely AI-made skills are hot garbage, and that's putting it mildly.
- >
- > That said, if you have any problems with code that is written by AI - you've been warned. But, then again, why would you be interested in AI-related configs and skills in the first place... `¯\_(ツ)_/¯`
- ## Why claude-toolbox?
- Tools like Claude Code and Codex are powerful on their own, but LLMs don't know your development workflow. This project started as a way for me to streamline claude configurations across all my projects without needing to copy-paste things. With time, patterns and re-curring prompts evolved into skills and agents. Currently, claude-toolbox gives you two things:
- **A minimal, opinionated Claude Code and Codex configuration** — sensible permission baselines, a rich statusline, MCP server wiring, and sync infrastructure to keep it all up to date across your projects. Think of it as a dotfiles repo for Claude Code and Codex.
- **A structured development pipeline** — 16 workflow and utility skills with explicit multi-language support that take you from idea through design, implementation, code review, testing, to documentation, with persistent knowledge that carries across sessions.
- ```
- /kk:design → /kk:review-design → /kk:implement → /kk:review-code → /kk:test → /kk:document
- ```
- Out of the box you get:
- - **16 workflow and utility skills** — a complete development pipeline invoked as `/kk:<skill-name>`, plus utilities such as `/kk:clarify-docs` for improving existing documentation, PR drafts and issue descriptions, and explicit `/kk:handoff` publication of task context to a secret GitHub gist.
- - **Multi-language support** — precise and distinct instructions from design, to implementation, to testing, to review for: go, java, js/ts, kotlin, kubernetes, and python
- - **Multi-model code review** — independent reviewers using sub-agents and external models (Gemini, etc.)
- - **Persistent knowledge base** — findings, decisions, and conventions that survive across sessions via Capy
- - **Up-to-date library docs** — always-current documentation lookup via Context7
- - **Battle-tested configuration** — permissions, statusline themes, hooks, sensible defaults
- ## Choose Your Path
- **Starting a new project?** Use the template — you get the full configuration and plugin pre-wired, plus sync infrastructure to pull future updates.
- → [Template Setup](https://serpro69.github.io/claude-toolbox/latest/getting-started/template-setup/)
- **Existing project, want the full setup?** Adopt the configuration, plugin, and sync infrastructure without creating from the template.
- → [Adopting into Existing Repositories](https://serpro69.github.io/claude-toolbox/latest/getting-started/adopting/)
- **Just want the skills?** Install the kk plugin — no template needed.
- → [Plugin-Only Setup](https://serpro69.github.io/claude-toolbox/latest/getting-started/plugin-only/)
- ## Try It
- After setup, try the core workflow:
- For an optional conversation first, use `/kk:brainstorm` to think through a technical idea. It adapts the interview to your next decision and ends with a chat recap of decisions, rationale, and open assumptions. It creates no files or automatic handoff; request `/kk:design` when you want written planning.
- 1. **Write a plan.** Type `/kk:design` and describe a feature you want to build. Claude will ask refinement questions and confirm decisions, then produce design docs, an implementation plan, and a task list in `docs/feat/wip/`.
- 2. **Review the design.** Run `/kk:review-design your-feature` to catch gaps before writing code.
- 3. **Build it.** Type `/kk:implement` — Claude establishes the task's behavior and compatibility constraints, implements it, and supplies current evidence to independent review. Standalone fixes also work without design documents.
- 4. **Review the code.** `/kk:review-code` traces intended behavior, unchanged callers and affected compatibility contracts alongside SOLID, security and quality checks. Use `/kk:review-code:isolated` for independent review without the implementation conversation: an internal reviewer plus external review through PAL, using an API model when one is configured and otherwise your installed CLIs from other vendors (see [isolated reviews](docs/user-guide/skills.md#isolated-reviews-and-external-models)).
- Reviews distinguish current regressions from inherited issues and code support
- from deployment readiness. Missing evidence stays explicit; green tests support
- the paths exercised. Verification is proportionate to the change, while explicit
- repository and release checks remain required. See
- [functional review and implementation](docs/user-guide/skills.md#functional-review-and-implementation)
- for examples and limits.
- This is the core loop. See the [Skills documentation](https://serpro69.github.io/claude-toolbox/latest/user-guide/skills/) for all available skills and the full workflow pipeline.
- To clarify a bug report or feature request, use `/kk:clarify-docs issue-draft.md`
- or supply an issue URL or pasted description with a local destination. The skill
- preserves evidence limits and produces a local draft; it does not publish or
- implement the issue. See [issue-description examples](docs/user-guide/skills.md#clarify-an-issue-description)
- for output selection and audience rules. Clarification remains optional.
- ## Examples
- Examples of actual Claude Code workflows executed using this template's configs, skills, and tools: [examples/](./examples)
- ## Contributing
- Contributions are welcome! See the [Contributing guide](https://serpro69.github.io/claude-toolbox/latest/contributing/) for guidelines, [Architecture](https://serpro69.github.io/claude-toolbox/latest/contributing/architecture/) for how components fit together, and [Testing](https://serpro69.github.io/claude-toolbox/latest/contributing/testing/) for test conventions.
- ## License
- Copyright © 2025 - present, [serpro69](https://github.com/serpro69)
- Distributed under the Apache License 2.0.
- See [`LICENSE.md`](https://github.com/serpro69/claude-toolbox/blob/master/LICENSE.md) file for more information.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.