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.
npx agentmods add settings/gceico/claude-make-it-rain/settingsgit clone --depth 1 https://github.com/gceico/claude-make-it-rainWrote 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/gceico/claude-make-it-rain/settings)<a href="https://agentmods.dev/settings/gceico/claude-make-it-rain/settings"><img src="https://agentmods.dev/badge/settings/gceico/claude-make-it-rain/settings.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
claude-make-it-rain scanned grade A with 0 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 3d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-settings.json",
"permissions": {
"allow": [
"Bash(npm test)",
"Bash(npm test:*)",
"Bash(npm start)",
"Bash(npm run test:*)",
"Bash(node --version)",
"Bash(node --test:*)",
"Bash(git status)",
"Bash(git diff:*)",
"Bash(git log:*)"
]
}
}
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.
- 3d ago First seen · 17 lines scan A b7f3f680ab93
claude-make-it-rain is a settings file published in the GitHub repository gceico/claude-make-it-rain (10 stars, last pushed 1mo ago), 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 A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other settings, from other repositories
manifest
Agent settings declaring 1 hook event (PostToolUse).
tokentelemetry
Agent settings declaring 1 hook event (PreToolUse).
openclaw-dashboard
Agent settings declaring 1 hook event (PreToolUse).
mcp-token-tracker
Agent settings declaring 1 hook event (PostToolUse).
learn-mcp-agent-ledger
Agent settings declaring 84 allowed tools.
tokentab
Agent settings declaring 3 hook events (PreToolUse, SessionStart, Stop).