agent-toolkit
CLAUDE.md2 starsChanged 4 months agoMITView on GitHub
Guidance for Claude Code when working on this repository. Everything in AGENTS.md applies, so start there for the repo map, principles, and how to add each component type. This file only adds what's specific to Claude Code. This repo is also a Claude Code plugin (single bundled plugin, agent-toolkit), which is the primary target. - Plugin manifests live in .claude-plugin/ — plugin.json (registers ./skills, ./commands, and each bundled agent) and marketplace.json (marketplace dius-agent-toolkit, plugin agent-toolkit, sourced from GitHub DiUS/agent-toolkit). Keep…
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- codebase-discoverySkill
- knowledge-curationSkill
- prd-to-steel-threadSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 40
Run the verification gate (also enforced in CI):
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CLAUDE.md
Guidance for Claude Code when working on this repository. Everything in AGENTS.md applies, so start there for the repo map, principles, and how to add each component type. This file only adds what's specific to Claude Code.
@AGENTS.md
Claude Code specifics
This repo is also a Claude Code plugin (single bundled plugin, agent-toolkit), which is
the primary target.
- Plugin manifests live in
.claude-plugin/—plugin.json(registers./skills,./commands, and each bundled agent) andmarketplace.json(marketplacedius-agent-toolkit, pluginagent-toolkit, sourced from GitHubDiUS/agent-toolkit). Keep both valid JSON;scripts/validate.jschecks them. - Subagents in
agents/are Claude Code workers a skill can delegate to (for example, to keep the main context lean or to run an isolated pass). Each is registered in theagentsarray ofplugin.json. On non-Claude hosts they're absent, and the skill falls back to a generic sub-agent or inline work. Keep that fallback path intact when editing skill behaviour. - Commands in
commands/register as slash commands automatically via the plugin. They're a Claude Code convention; other agents fall back to reading the referenced skill directly. - Hooks are opt-in. Nothing under
hooks/is wired intoplugin.json. Don't make a hook a dependency of any skill, command or agent in this repo.
Testing changes locally
# load the plugin from this working tree
claude --plugin-dir /path/to/agent-toolkit
# preview skill discovery for the npx-skills channel
npx skills add . --listBefore committing
Run the verification gate (also enforced in CI):
node scripts/validate.jsDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

