Borrowing it
Nothing to install: this file belongs to ruvnet/metaharness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ruvnet/metaharness/main/kimi-k3-harness/.claude/settings.jsongit clone --depth 1 https://github.com/ruvnet/metaharnessWrote 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/settings/ruvnet/metaharness/settings)<a href="https://agentmods.dev/settings/ruvnet/metaharness/settings"><img src="https://agentmods.dev/badge/settings/ruvnet/metaharness/settings/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/settings/ruvnet/metaharness/settings"><img src="https://agentmods.dev/badge/settings/ruvnet/metaharness/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade C, and why
metaharness scanned grade C with 1 finding 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"Bash(rm -rf*)" What it actually says
{
"permissions": {
"allow": [
"Bash(npx kimi-k3-harness*)",
"mcp__kimi-k3-harness__*",
"mcp__code_index__*",
"Bash(npm test*)",
"Bash(npm run*)",
"Bash(git diff*)",
"Bash(git status*)",
"Bash(git log*)"
],
"deny": [
"Read(./.env)",
"Read(./.env.*)",
"Bash(git push*)",
"Bash(rm -rf*)"
]
},
"mcpServers": {
"kimi-k3-harness": {
"command": "npx",
"args": [
"-y",
"kimi-k3-harness@latest",
"mcp",
"start"
]
},
"code_index": {
"command": "npx",
"args": [
"-y",
"kimi-k3-harness@latest",
"mcp",
"index"
]
}
}
}
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.
- 1mo ago First seen · 41 lines scan C b4b05318b04b
metaharness is a settings file published in the GitHub repository ruvnet/metaharness (709 stars, last pushed yesterday), 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 C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other settings, from other repositories
supabase
Agent settings declaring 2 hook events (SessionStart, PostToolUse).
superset
Agent settings declaring 1 hook event (PreToolUse).
RuView
Agent settings declaring 8 hook events (PreToolUse, PostToolUse, UserPromptSubmit, SessionStart) and 4 allowed tools.
orm
Agent settings declaring 4 hook events (PreToolUse, PostToolUse, WorktreeCreate, Stop) and 21 allowed tools.
claude-cookbooks
Agent settings declaring 2 hook events (SessionStart, PreToolUse).
claude-code-best-practice
Agent settings declaring 30 hook events (PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure) and 24 allowed tools.