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/rmednitzer/aiops-mcp/settingsgit clone --depth 1 https://github.com/rmednitzer/aiops-mcpWrote 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/rmednitzer/aiops-mcp/settings)<a href="https://agentmods.dev/settings/rmednitzer/aiops-mcp/settings"><img src="https://agentmods.dev/badge/settings/rmednitzer/aiops-mcp/settings.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
settings scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
"Bash(curl:*)", What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-settings.json",
"permissions": {
"allow": [
"Bash(uv:*)",
"Bash(uvx:*)",
"Bash(ruff:*)",
"Bash(python:*)",
"Bash(python3:*)",
"Bash(pytest:*)",
"Bash(mypy:*)",
"Bash(make check)",
"Bash(make lint)",
"Bash(make format)",
"Bash(make type-check)",
"Bash(make test)",
"Bash(make coverage)",
"Bash(make schema)",
"Bash(make schema-check)",
"Bash(make eval)",
"Bash(make validate-compliance)",
"Bash(make helm-test)",
"Bash(make ci-success)",
"Bash(make docs)",
"Bash(pre-commit run:*)",
"Bash(pip list)",
"Bash(pip list:*)",
"Bash(pip show:*)",
"Bash(pip freeze)",
"Bash(pipx list)",
"Bash(pipx run:*)",
"Bash(helm lint:*)",
"Bash(helm template:*)",
"Bash(helm unittest:*)"
],
"deny": [
"Read(./.env)",
"Read(./.env.*)",
"Read(**/.env)",
"Read(**/.env.*)",
"Read(**/secrets/**)",
"Read(~/.ssh/**)",
"Read(~/.aws/**)",
"Read(~/.config/gh/**)",
"Read(**/*.pem)",
"Read(**/id_rsa*)",
"Bash(curl:*)",
"Bash(wget:*)",
"Bash(git push --force)",
"Bash(git push --force:*)",
"Bash(git push -f)",
"Bash(git push -f:*)",
"Bash(git push * --force)",
"Bash(git push * --force *)",
"Bash(git push * -f)",
"Bash(git push * -f *)"
]
}
}
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 · 60 lines scan A 9173243722f8
settings is a settings file published in the GitHub repository rmednitzer/aiops-mcp (0 stars, last pushed 4d ago), 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 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other settings, from other repositories
Q4_learning
Agent settings declaring 4 allowed tools.
slack-mcp
Agent settings configuring enabledPlugins.
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.