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/ivanbbaev/servicenow-mcp-ai/settingsgit clone --depth 1 https://github.com/IvanBBaev/servicenow-mcp-aiWrote 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/ivanbbaev/servicenow-mcp-ai/settings)<a href="https://agentmods.dev/settings/ivanbbaev/servicenow-mcp-ai/settings"><img src="https://agentmods.dev/badge/settings/ivanbbaev/servicenow-mcp-ai/settings.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
settings 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.
What it actually says
{
"permissions": {
"allow": [
"Bash(node --test test/*.test.js)",
"Bash(node --test test/*)",
"Bash(export PATH=\"$HOME/.nvm/versions/node/v22.22.2/bin:$PATH\")",
"Bash(npm run build)",
"Bash(npm run lint)",
"Bash(npx tsc --noEmit *)",
"Bash(npx tsc --noEmit)",
"Bash(git add *)",
"Bash(git commit *)"
]
}
}
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 · 16 lines scan A dbad94c8f924
settings is a settings file published in the GitHub repository IvanBBaev/servicenow-mcp-ai (8 stars, last pushed 6d 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
dynamic-mcp
Agent settings configuring enabledMcpjsonServers, enableAllProjectMcpServers, enabledPlugins.
swiss-cultural-heritage-mcp
Agent settings declaring 1 hook event (SessionStart).
swiss-food-safety-mcp
Agent settings declaring 1 hook event (SessionStart).
backlog-mcp
Agent settings declaring 1 hook event (SessionStart).
xbrain
Agent settings declaring 3 hook events (SessionStart, PostToolUse, PreToolUse).
supabase
Agent settings declaring 2 hook events (SessionStart, PostToolUse).