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/aptica-solutions/a-mcp-runmeter/settingsgit clone --depth 1 https://github.com/Aptica-Solutions/a-mcp-runmeterWrote 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/aptica-solutions/a-mcp-runmeter/settings)<a href="https://agentmods.dev/settings/aptica-solutions/a-mcp-runmeter/settings"><img src="https://agentmods.dev/badge/settings/aptica-solutions/a-mcp-runmeter/settings.svg" alt="Measured on agentmods" height="20"></a>Grade F, and why
a-mcp-runmeter scanned grade F with 4 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
"Bash(sudo rm *)", Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
"Bash(curl * | sh)", 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 * | sh)", What it actually says
{
"permissions": {
"deny": [
"Bash(rm -rf *)",
"Bash(sudo rm *)",
"Bash(curl * | sh)",
"Bash(curl * | bash)",
"Bash(wget * | sh)",
"Bash(wget * | bash)",
"Bash(chmod 777 *)",
"Bash(git push --force)",
"Bash(git push -f)",
"Bash(DROP TABLE*)",
"Bash(DROP DATABASE*)"
]
},
"hooks": {
"UserPromptSubmit": [
{
"hooks": [
{
"type": "command",
"command": "pwsh -NoProfile -File .claude/hooks/survey-gate.ps1"
}
]
}
]
},
"attribution": {
"commit": "",
"pr": "",
"sessionUrl": false
}
}
What else settings.json configures
This page is one entry in a file that holds 2. 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.
- 3d ago First seen · 35 lines scan F b17c9224421b
a-mcp-runmeter is a settings file published in the GitHub repository Aptica-Solutions/a-mcp-runmeter (0 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 F with 4 findings (asks for root, downloads and executes remote code, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other settings, from other repositories
promptfoo
Agent settings declaring 2 hook events (PreToolUse, PostToolUse).
gateway
Agent settings declaring 3 hook events (PostToolUse, PreToolUse, Notification) and 23 allowed tools.
agentic-lab
Agent settings declaring 1 hook event (PreToolUse) and 10 allowed tools.
unraid
Agent settings configuring hooks.
settings
Agent settings declaring 1 hook event (SessionStart).
MCPSpy
Agent settings declaring 8 allowed tools.