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/luligu/matterbridge-shelly/settingsgit clone --depth 1 https://github.com/Luligu/matterbridge-shellyWrote 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/luligu/matterbridge-shelly/settings)<a href="https://agentmods.dev/settings/luligu/matterbridge-shelly/settings"><img src="https://agentmods.dev/badge/settings/luligu/matterbridge-shelly/settings.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
matterbridge-shelly 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 4d 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.
This is a copy
100% identical to matterbridge-hass — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-settings.json",
"_comment": "Claude settings v. 1.0.6",
"permissions": {
"deny": [
"Read(.env)",
"Read(.env.*)",
"Read(**/.env)",
"Read(**/.env.*)",
"Read(**/secrets/**)",
"Bash(git pull:*)",
"Bash(git merge:*)",
"Bash(git push:*)",
"Bash(git rebase:*)",
"Bash(git commit --amend:*)",
"Bash(git reset --hard:*)",
"Bash(git filter-branch:*)",
"Bash(git branch -D:*)",
"Bash(git branch -d:*)",
"Bash(git tag -d:*)",
"Bash(git stash:*)",
"Bash(git reflog expire:*)",
"Bash(git reflog delete:*)"
],
"ask": [
"Bash(git commit:*)",
"Bash(npm install:*)",
"Bash(npm i:*)",
"Bash(npm uninstall:*)",
"Bash(bun install:*)",
"Bash(bun i:*)",
"Bash(bun uninstall:*)",
"Bash(bun add:*)",
"Bash(bun remove:*)"
],
"allow": [
"Read",
"Bash(npm run)",
"Bash(npm run typecheck:*)",
"Bash(npm run build:*)",
"Bash(npm run test:*)",
"Bash(npm run lint:*)",
"Bash(npm run format:*)",
"Bash(bun test:*)",
"Bash(npx vitest:*)",
"Bash(vitest:*)",
"Bash(npx oxfmt:*)",
"Bash(oxfmt:*)",
"Bash(npx oxlint:*)",
"Bash(oxlint:*)",
"Bash(npx tsc:*)",
"Bash(tsc:*)",
"Bash(grep:*)",
"Bash(cd:*)",
"Bash(tail:*)",
"Bash(find:*)",
"Bash(echo:*)",
"Bash(head:*)",
"Bash(cat:*)",
"Bash(ls:*)"
]
}
}
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.
- 4d ago First seen · 64 lines scan A 68539e4c61ef
matterbridge-shelly is a settings file published in the GitHub repository Luligu/matterbridge-shelly (138 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 A with 0 findings. It is 100% identical to matterbridge-hass, differing in 0 lines, and is treated as a copy.
Other settings, from other repositories
supabase
Agent settings declaring 2 hook events (SessionStart, PostToolUse).
superset
Agent settings declaring 1 hook event (PreToolUse).
claude-cookbooks
Agent settings declaring 2 hook events (SessionStart, PreToolUse).
claude-code-best-practice
Agent settings declaring 30 hook events (PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure) and 24 allowed tools.
electron
Agent settings declaring 17 allowed tools.
uv
Agent settings declaring 2 hook events (SessionStart, PostToolUse).