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.
git clone --depth 1 https://github.com/prime-radiant-inc/scenariosWrote 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/mcp/prime-radiant-inc/scenarios/claude-code-scenario-assistant)<a href="https://agentmods.dev/mcp/prime-radiant-inc/scenarios/claude-code-scenario-assistant"><img src="https://agentmods.dev/badge/mcp/prime-radiant-inc/scenarios/claude-code-scenario-assistant/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/prime-radiant-inc/scenarios/claude-code-scenario-assistant"><img src="https://agentmods.dev/badge/mcp/prime-radiant-inc/scenarios/claude-code-scenario-assistant.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
scenario-assistant 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 10d 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
{
"scenario-assistant": {
"command": "uv",
"args": [
"run",
"../../tools/mcp_server.py"
]
}
}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.
- 10d ago First seen · 9 lines scan A 212a4f5d54a4
scenario-assistant is an MCP server published in the GitHub repository prime-radiant-inc/scenarios (10 stars, last pushed 3mo ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
web-fetcher
MCP server "web-fetcher" as configured in akanthed/SecureAI-Scan. Runs locally from the some-mcp-fetch-server npm package. Needs 1 environment variable to run.
local-dev
MCP server "local-dev", hosted remotely at localhost, as configured in akanthed/SecureAI-Scan.
remote-tools
MCP server "remote-tools", hosted remotely at tools.example.com, as configured in akanthed/SecureAI-Scan.
shellward
AI agent security: 7 MCP tools for injection detection, PII scanning, command safety, DLP. Runs locally from the shellward npm package. Needs 3 environment variables to run.
stripe-mcp
MCP server "stripe-mcp" as configured in apisec-inc/AI-Surface. Runs locally from the @stripe/mcp-server npm package.
github-mcp
MCP server "github-mcp", hosted remotely at mcp.github.com, as configured in apisec-inc/AI-Surface.