Borrowing it
Nothing to install: this file belongs to 777genius/social-monitor. 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/777genius/social-monitor/main/.claude/settings.jsongit clone --depth 1 https://github.com/777genius/social-monitorWrote 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/777genius/social-monitor/settings)<a href="https://agentmods.dev/settings/777genius/social-monitor/settings"><img src="https://agentmods.dev/badge/settings/777genius/social-monitor/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/777genius/social-monitor/settings"><img src="https://agentmods.dev/badge/settings/777genius/social-monitor/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade C, and why
social-monitor 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 12d 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(//**/.netrc)", How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"permissions": {
"disableAutoMode": "disable",
"disableBypassPermissionsMode": "disable",
"deny": [
"Read(//**/.env)",
"Read(//**/.env.local)",
"Read(//**/.env.production)",
"Read(//**/.env.staging)",
"Read(//**/.env.beta)",
"Read(//**/.env.development)",
"Read(//**/.envrc)",
"Read(//**/.npmrc)",
"Read(//**/.pypirc)",
"Read(//**/.netrc)",
"Read(//**/secrets/**)",
"Read(//**/credentials/**)",
"Read(//**/.ssh/**)",
"Read(//**/.aws/**)",
"Read(//**/.azure/**)",
"Read(//**/.kube/**)",
"Read(//**/.config/gh/**)",
"Read(//**/.config/gcloud/**)",
"Read(//**/.config/stripe/**)",
"Read(//**/.config/vercel/**)",
"Read(//**/.config/supabase/**)",
"Read(//**/.docker/config.json)",
"Read(//**/*.pem)",
"Read(//**/*.key)",
"Read(//**/id_rsa)",
"Read(//**/id_ed25519)",
"Edit(//**/.env)",
"Edit(//**/.env.local)",
"Edit(//**/.env.production)",
"Edit(//**/.env.staging)",
"Edit(//**/.env.beta)",
"Edit(//**/.env.development)",
"Edit(//**/.envrc)",
"Edit(//**/.npmrc)",
"Edit(//**/.pypirc)",
"Edit(//**/.netrc)",
"Edit(//**/secrets/**)",
"Edit(//**/credentials/**)",
"Edit(//**/.ssh/**)",
"Edit(//**/.aws/**)",
"Edit(//**/.azure/**)",
"Edit(//**/.kube/**)",
"Edit(//**/.config/gh/**)",
"Edit(//**/.config/gcloud/**)",
"Edit(//**/.config/stripe/**)",
"Edit(//**/.config/vercel/**)",
"Edit(//**/.config/supabase/**)",
"Edit(//**/.docker/config.json)",
"Edit(//**/*.pem)",
"Edit(//**/*.key)",
"Edit(//**/id_rsa)",
"Edit(//**/id_ed25519)",
"Write(//**/.env)",
"Write(//**/.env.local)",
"Write(//**/.env.production)",
"Write(//**/.env.staging)",
"Write(//**/.env.beta)",
"Write(//**/.env.development)",
"Write(//**/.envrc)",
"Write(//**/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.
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.
- 12d ago First seen · 130 lines scan C ed80ea3cb491
social-monitor is a settings file published in the GitHub repository 777genius/social-monitor (46 stars, last pushed today), 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 1 finding (reaches for credential files). 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-code-best-practice
Agent settings declaring 30 hook events (PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure) and 24 allowed tools.
claude-cookbooks
Agent settings declaring 2 hook events (SessionStart, PreToolUse).