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 nikitaCodeSave/claude-code-harnessnpx agentmods add plugins/nikitacodesave/claude-code-harness/marketplacegit clone --depth 1 https://github.com/nikitaCodeSave/claude-code-harnessGrade A, and why
claude-code-harness 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 2d 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
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "claude-code-harness",
"owner": {
"name": "nikitaCodeSave",
"email": "[email protected]"
},
"metadata": {
"description": "The claude-code-harness kit — designs, bootstraps, audits, and extends a Claude Code harness (.claude/ + root CLAUDE.md), plus the devlog continuity companion. Opinion: under a capable model, less harness yields more productivity."
},
"plugins": [
{
"name": "claude-code-harness",
"source": "./plugins/harness",
"description": "Designs, bootstraps, audits, and extends a Claude Code harness (.claude/ + root CLAUDE.md). Bootstrap / Audit / Extend / Explain modes. Ships a skill and its references — no agents, no commands, no hooks.",
"category": "workflow",
"keywords": ["claude-code", "harness", "plugin-development", "bootstrap", "audit"]
},
{
"name": "devlog",
"source": "./plugins/devlog",
"description": "Records significant changes to .claude/devlog/ — the episodic 'what changed and why' continuity layer, one markdown entry per feature/fix/decision, with index+digest regeneration and a SessionStart digest that auto-surfaces recent devlog + active progress. The harness kit recommends this; installing it makes that guidance runnable.",
"category": "workflow",
"keywords": ["claude-code", "devlog", "changelog", "continuity", "session-handoff"]
}
]
}
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.
- 2d ago First seen · 28 lines scan A 0adb2ada075c
claude-code-harness is a plugin published in the GitHub repository nikitaCodeSave/claude-code-harness (5 stars, last pushed 3d 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
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.