agentmods.dev

openharness: Settings file for Claude Code

.claude/settings.json

openharness is a settings file for Claude Code from mifunedev/openharness. Its token cost is not measured, scanned C, original, Apache-2.0.

Project settings that connect a debugging service, restrict access to credential files, and define safety hooks around tool use, stopping, and notifications.

In plain words
What is it for?
Debugging through the configured service and controlling which sensitive files and settings the agent may read or change.
Why use it?
They reduce the chance of exposing secrets such as cloud credentials, private keys, or environment files while the agent works.

Settings file for Claude Code

Written for Claude Code: $CLAUDE_PROJECT_DIR variable. Also seen: names the NotebookEdit tool.

This is mifunedev/openharness's own configuration. It tells Claude Code how to work on openharness itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything openharness configures →

One of 4 entries in settings.json upstream. Installing this one merges just its entry into your config; the other 3 are separate, each on its own page.

not rated 37repo changed 1mo ago C scan tokens not measured original Apache-2.0
View source ↗ mifunedev/openharness oh.mifune.dev
Reuse

Borrowing it

Nothing to install: this file belongs to mifunedev/openharness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mifunedev/openharness/main/.claude/settings.json
Clone the repo
git clone --depth 1 https://github.com/mifunedev/openharness

Made for: Claude Code.

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

agentmods badge for openharness

README.md
[![agentmods](https://agentmods.dev/badge/settings/mifunedev/openharness/settings/github.svg)](https://agentmods.dev/settings/mifunedev/openharness/settings)
Your own site
<a href="https://agentmods.dev/settings/mifunedev/openharness/settings"><img src="https://agentmods.dev/badge/settings/mifunedev/openharness/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.

agentmods 80×15 button for openharness

Your own site · 80×15
<a href="https://agentmods.dev/settings/mifunedev/openharness/settings"><img src="https://agentmods.dev/badge/settings/mifunedev/openharness/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade C, and why

openharness scanned grade C with 2 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 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.

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

"Read(file_path=**/.aws/credentials)",

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

"Read(file_path=**/.wget-hsts)",
.claude/settings.json · 158 lines

How it starts

The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.

{
  "enabledMcpjsonServers": ["debugmcp"],
  "permissions": {
    "deny": [
      "Read(file_path=**/.env*)",
      "Read(file_path=**/*.pem)",
      "Read(file_path=**/*.key)",
      "Read(file_path=**/*.cert)",
      "Read(file_path=**/*.p12)",
      "Read(file_path=**/*id_rsa*)",
      "Read(file_path=**/*id_ed25519*)",
      "Read(file_path=**/.aws/credentials)",
      "Read(file_path=**/.aws/config)",
      "Read(file_path=**/.gcp/**)",
      "Read(file_path=**/settings.local.json)",
      "Edit(file_path=**/settings.local.json)",
      "Read(file_path=**/.config)",
      "Read(file_path=**/.config/**)",
      "Edit(file_path=**/.config)",
      "Edit(file_path=**/.config/**)",
      "Bash(command=*/.config/*)",
      "Bash(command=*/.config)",
      "Read(file_path=**/.config/gcloud/**)",
      "Read(file_path=**/.azure/**)",
      "Read(file_path=**/.kube/config)",
      "Read(file_path=**/.docker/config.json)",
      "Read(file_path=**/.npmrc)",
      "Read(file_path=**/.pypirc)",
      "Read(file_path=**/.cargo/credentials*)",
      "Read(file_path=**/.git-credentials)",
      "Read(file_path=**/.netrc)",
      "Read(file_path=**/.config/gh/hosts.yml)",
      "Read(file_path=**/.config/gh/config.yml)",
      "Read(file_path=**/.claude/.credentials.json)",
      "Read(file_path=**/.anthropic/**)",
      "Read(file_path=**/.pi/**/auth.json)",
      "Read(file_path=**/.gnupg/**)",
      "Read(file_path=**/.bash_history)",
      "Read(file_path=**/.zsh_history)",
      "Read(file_path=**/.psql_history)",
      "Read(file_path=**/.python_history)",
      "Read(file_path=**/.node_repl_history)",
      "Read(file_path=**/.wget-hsts)",
      "Bash(command=*cat*.env*)",
      "Bash(command=*printenv*)",
      "Bash(command=*inspect*Config.Env*)",
      "Bash(command=*inspect*ContainerSpec.Env*)",
      "Bash(command=*inspect*{{json .}}*)",
      "Bash(command=*inspect*{{ json . }}*)",
      "Bash(command=*inspect*{{.}}*)",
      "Bash(cat **/.env*)",
      "Bash(com

Read the full file on GitHub · 158 lines

Same file

What else settings.json configures

This page is one entry in a file that holds 4. Installing the file brings all of them; each is measured and scanned on its own page.

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. 1mo ago Changed · -5 lines 0ed528bb9159
  2. 1mo ago First seen · 163 lines scan C 0307b60a0b9c

Subscribe to this mod's changes

openharness is a settings file published in the GitHub repository mifunedev/openharness (37 stars, last pushed 1mo ago), licensed Apache-2.0. 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 2 findings (reaches for credential files, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude CodeLangChainNVIDIAcodexdeepagentsdocker
Related

Other settings, from other repositories

supabase

Agent settings declaring 2 hook events (SessionStart, PostToolUse).

supabase/supabase · not measured

superset

Agent settings declaring 1 hook event (PreToolUse).

apache/superset · not measured

RuView

Agent settings declaring 8 hook events (PreToolUse, PostToolUse, UserPromptSubmit, SessionStart) and 4 allowed tools.

ruvnet/RuView · not measured

claude-cookbooks

Agent settings declaring 2 hook events (SessionStart, PreToolUse).

anthropics/claude-cookbooks · not measured

orm

Agent settings declaring 4 hook events (PreToolUse, PostToolUse, WorktreeCreate, Stop) and 21 allowed tools.

prisma/orm · not measured

claude-code-best-practice

Agent settings declaring 30 hook events (PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure) and 24 allowed tools.

shanraisshan/claude-code-best-practice · not measured