Borrowing it
Nothing to install: this file belongs to HarmonicSecurity/claudit-sec. 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/HarmonicSecurity/claudit-sec/main/CLAUDE.mdgit clone --depth 1 https://github.com/HarmonicSecurity/claudit-secWrote 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/instructions/harmonicsecurity/claudit-sec/claude-md)<a href="https://agentmods.dev/instructions/harmonicsecurity/claudit-sec/claude-md"><img src="https://agentmods.dev/badge/instructions/harmonicsecurity/claudit-sec/claude-md/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/instructions/harmonicsecurity/claudit-sec/claude-md"><img src="https://agentmods.dev/badge/instructions/harmonicsecurity/claudit-sec/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.02074 | $0.02074 |
| Opus 5.5 | $0.00830 | $0.00830 |
| Sonnet 5.5 | $0.00415 | $0.00415 |
| Haiku 4.5 | $0.00207 | $0.00207 |
Grade B, and why
claudit-sec CLAUDE.md scanned grade B with 3 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
When run as root (uid 0) — which is how MDMs like FleetDM, Jamf, Mosyle, and CrowdStrike RTR execute scripts — the script automatically scans all users with Claude data. No flags needed. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
| Claude Code Settings | `~/.claude/settings.json` | Permission grants | Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Enumerates other installed skillslowAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
~/.skills/skills/*/SKILL.md # Alt skills dir ~/.claude/skills/*/SKILL.md # Claude Code user skills Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDIT-SEC — Claude Security Audit Tool
Project Overview
CLAUDIT-SEC is a read-only, single-file security audit tool for macOS that inspects Claude Desktop and Claude Code configuration, scheduled tasks, extensions, plugins, skills, permissions, and runtime state.
claude_audit.sh— Zsh (~1900 lines, requiresjq) — designed for MDM/CrowdStrike RTR style deployment
This project is built and maintained using Claude Code. This file provides architecture context and development guidelines that Claude Code uses when working on the codebase.
Architecture
The script follows this structure:
- Preflight checks — OS validation, dependency checks
- User context detection — single user, explicit
--user, or all-users scan - Session directory discovery — finds
local-agent-mode-sessions/org/user/paths - 14 data collectors — each reads specific config files and populates findings
- Finding aggregation — counts by severity (WARN, INFO, REVIEW)
- 3 output renderers — ASCII (ANSI color + Unicode tables), HTML (dark theme), JSON (SIEM-ready)
Data Collectors
| Collector | Source Files | Key Findings |
|---|---|---|
| Desktop Settings | claude_desktop_config.json → preferences |
keepAwakeEnabled, allowAllBrowserActions, menuBar, sidebar |
| Cowork Settings | cowork_settings.json, config.json |
scheduledTasks, webSearch, networkMode |
| MCP Servers | claude_desktop_config.json → mcpServers |
Server names, commands, env var keys |
| Plugins | installed_plugins.json, remote manifest, marketplace cache |
installed/remote/cached plugins |
| Plugin Hooks | hooks/hooks.json in plugin directories |
Shell commands on lifecycle events |
| Connectors | local_*.json → remoteMcpServersConfig, .mcp.json |
web/desktop/not_connected, egressAllowedDomains, disabledMcpTools |
| Skills | User skills (6 paths), installed plugin skills (3 paths) — see Key Paths | SKILL.md frontmatter parsing |
| Scheduled Tasks | scheduled-tasks.json |
Cron expressions with english translation |
| Extensions (DXT) | extensions-installations.json |
Signature status, dangerous tools |
| Extension Settings | Claude Extensions Settings/*.json |
Allowed directories |
| Blocklist | extensions-blocklist.json |
Governance control presence |
| Claude Code Settings | ~/.claude/settings.json |
Permission grants |
| Runtime | pgrep, pmset, crontab, LaunchAgents | Running processes, sleep assertions |
| Cookies | Cookies, Cookies-journal |
Presence and permissions |
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 · 162 lines · 2,074 tokens per session scan B 94d8cde7e650
claudit-sec CLAUDE.md is an instructions file published in the GitHub repository HarmonicSecurity/claudit-sec (300 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 2,074 tokens to every session, about $0.0083 per session on Opus 5.5. A static security scan graded it B with 3 findings (asks for root, reads agent configuration directories, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.