settings

A configuration file that gives the coding agent access to two external services: one for running a Kimi K3 harness and one for indexing code.

In plain words
What is it for?
Use it to configure approved tools, run tests and npm commands, inspect code indexes, and prevent access to environment files, force-pushing, and recursive deletion.
Why use it?
It records which tools the agent may use and which commands or files are allowed or blocked, so project work follows set boundaries.

Settings file for Claude Code

Install

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.

agentmods
npx agentmods add settings/ruvnet/metaharness/settings
Clone the repo
git clone --depth 1 https://github.com/ruvnet/metaharness

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade C, and why

settings 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 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.

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*)"
kimi-k3-harness/.claude/settings.json · 41 lines

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"
      ]
    }
  }
}
Changes

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.

  1. 2d ago First seen · 41 lines scan C b4b05318b04b

Subscribe to this mod's changes

settings is a settings file published in the GitHub repository ruvnet/metaharness (624 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.