Borrowing it
Nothing to install: this file belongs to usrrname/cursorrules. 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/usrrname/cursorrules/main/.claude/settings.jsongit clone --depth 1 https://github.com/usrrname/cursorrulesWrote 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/usrrname/cursorrules/settings)<a href="https://agentmods.dev/settings/usrrname/cursorrules/settings"><img src="https://agentmods.dev/badge/settings/usrrname/cursorrules/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/usrrname/cursorrules/settings"><img src="https://agentmods.dev/badge/settings/usrrname/cursorrules/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade C, and why
cursorrules 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 2mo 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:/*)", Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
"Bash(curl:*)", How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"$schema": "https://json.schemastore.org/claude-code-settings.json",
"model": "claude-opus-4-5",
"permissions": {
"allow": [
"Read",
"Edit",
"Write",
"Bash(npm run:*)",
"Bash(git:*)",
"Bash(make:*)",
"Glob",
"Grep"
],
"deny": [
"Read(.env*)",
"Read(secrets/**)",
"Bash(rm -rf:/*)",
"Bash(sudo:*)",
"Edit(.git/**)"
],
"ask": [
"WebFetch",
"Bash(curl:*)",
"Bash(docker:*)"
],
"defaultMode": "acceptEdits"
},
"env": {
"NODE_ENV": "development"
},
"hooks": {
"PostToolUse": [
{
"matcher": "Edit|Write",
"hooks": [
{
"type": "command",
"command": "bash -c 'FILE=$(jq -r \".tool_input.file_path\" <<< \"$(cat)\"); if [[ \"$FILE\" == *.ts || \"$FILE\" == *.tsx || \"$FILE\" == *.js || \"$FILE\" == *.jsx ]]; then npx prettier --write \"$FILE\" 2>/dev/null || true; fi'",
"description": "Auto-format TypeScript/JavaScript files with Prettier"
}
]
}
],
"PreToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": ".claude/hooks/security-block.sh",
"description": "Block dangerous bash commands"
}
]
}
]
},
"mcpServers": {},
"includeCoAuthoredBy": true,
"cleanupPeriodDays": 30,
"personas": {
"BasicBitch": {
"name": "BasicBitch",
"description": "Reliable corporate developer who does exactly what's asked, nothing more. Adequate and dependable.",
"model": "claude-sonnet-4-5",
"prompt": "You are a mediocre but dependable software developer with textbook experience.\n\nCAPABILITIES:\n- Implement features with exact adherence to requirements\n- Apply design patterns adequately\n- Code review and technical documentation\n\nPERSONALITY:\n- Quiet, professional, and thorough\n- Writes maintainable code\n- OWhat else settings.json configures
This page is one entry in a file that holds 3. 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.
- 2mo ago First seen · 92 lines scan C 9a846d46c3b3
cursorrules is a settings file published in the GitHub repository usrrname/cursorrules (11 stars, last pushed 7mo ago), licensed ISC. 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 (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
cursorrules compared with settings from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| cursorrulesusrrname/cursorrules | Settings file | 11 | 7mo ago | ISC | C | — | Claude Code |
| supabasesupabase/supabase | Settings file | 115k | yesterday | Apache-2.0 | A | — | Claude Code |
| supersetapache/superset | Settings file | 75k | yesterday | Apache-2.0 | A | — | Claude Code |
| RuViewruvnet/RuView | Settings file | 103k | yesterday | MIT | A | — | Claude Code |
| claude-cookbooksanthropics/claude-cookbooks | Settings file | 54k | 2d ago | MIT | A | — | Claude Code |
| ormprisma/orm | Settings file | 48k | yesterday | Apache-2.0 | A | — | Claude Code |
| claude-code-best-practiceshanraisshan/claude-code-best-practice | Settings file | 69k | 2d ago | MIT | A | — | Claude Code |