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.
/plugin marketplace add stefan-jansen/claude-code-toolkitnpx agentmods add plugins/stefan-jansen/claude-code-toolkit/developmentgit clone --depth 1 https://github.com/stefan-jansen/claude-code-toolkitGrade A, and why
development 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 yesterday.
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": "development",
"version": "1.1.0",
"description": "Code development and quality assurance tools - analyze, test, fix, review",
"author": {
"name": "Claude Code Framework"
},
"keywords": [
"development",
"testing",
"quality",
"analysis",
"debugging",
"git"
],
"commands": [
"./commands/analyze.md",
"./commands/docs.md",
"./commands/fix.md",
"./commands/git.md",
"./commands/prepare-review.md",
"./commands/review.md",
"./commands/test.md"
],
"agents": [
"./agents/architect.md",
"./agents/code-reviewer.md",
"./agents/test-engineer.md"
],
"repository": "https://github.com/yourusername/claude-code-plugins",
"license": "MIT"
}
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.
- yesterday First seen · 33 lines scan A f8759cb5364e
development is a plugin published in the GitHub repository stefan-jansen/claude-code-toolkit (85 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-30.
Other plugins, from other repositories
codebase-documentor-for-aws
Analyze codebases to generate structured technical documentation with source-of-truth citations. Optimized for AWS workloads using CDK, CloudFormation, and Terraform.
sagemaker-ai
Build, train, and deploy AI models with deep AWS AI/ML expertise brought directly into your coding assistants, covering the surface area of Amazon SageMaker AI.
ctx
Plugin marketplace listing 1 plugin: ctx.
ctx
Fast local search and 'git blame' for agent sessions.
context-guard
Per-session context-window observability plus the first shipped consumer: a statusline wrapper tees each session's contextwindow fields to a per-session snapshot file, a zone resolver classifies usage into smart/acceptable/dumb bands (percentage bands plus window-class token bands, conservative-min combination, zones.
claude-memory
Keeps a repo's Claude Code memory layer healthy and under your control, against criteria derived from official Claude Code documentation. The audit skill checks the instruction/memory layer (CLAUDE.md, CLAUDE.local.md, .claude/rules/, auto-memory) with a deterministic script-backed spine plus judgment-tier checks. The.