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 mcp/patsypppe/sentinel/sentinel-workspacegit clone --depth 1 https://github.com/patsypppe/sentinelGrade A, and why
sentinel-workspace 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 yesterday.
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
{ "sentinel-workspace": { "command": "uvx", "args": [ "sentinel-workspace" ] } }
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.
- yesterday First seen · 8 lines scan A 8bded2dfbc74
sentinel-workspace is an MCP server published in the GitHub repository patsypppe/sentinel (0 stars, last pushed 6d ago), licensed MIT. 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
halomem
MCP server "halomem", hosted remotely, as configured in halofyai/halofy.
tower-mcp-example
MCP server "tower-mcp-example" as configured in joshrotenberg/tower-mcp. Launched with cargo run -p tower-mcp-examples --example getting_started. Needs 1 environment variable to run.
weather
MCP server "weather" as configured in joshrotenberg/tower-mcp. Launched with cargo run -p tower-mcp-examples --example weather_server. Needs 1 environment variable to run.
codegen-mcp
MCP server "codegen-mcp" as configured in joshrotenberg/tower-mcp. Launched with cargo run -p codegen-mcp. Needs 1 environment variable to run.
guard
MCP server "guard" as configured in open-covenant/covenant. Launched with https://github.com/open-covenant/covenant/releases/download/covguard-v0.1.1/cove.
sysknife
MCP server "sysknife" as configured in lacs-project/sysknife. Launched with sysknife-cli. Needs 1 environment variable to run.