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/wulfgardr/work-assistant/work-assistantgit clone --depth 1 https://github.com/Wulfgardr/work-assistantWrote 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/wulfgardr/work-assistant/work-assistant)<a href="https://agentmods.dev/mcp/wulfgardr/work-assistant/work-assistant"><img src="https://agentmods.dev/badge/mcp/wulfgardr/work-assistant/work-assistant.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
work-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 2d 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
{ "work-assistant": { "command": "uvx", "args": [ "work-assistant" ] } }
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.
- 2d ago First seen · 8 lines scan A 88b5012a3834
work-assistant is an MCP server published in the GitHub repository Wulfgardr/work-assistant (0 stars, last pushed 10d 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
mail-index
Local-first, read-only MCP server for recall over your Gmail: search, contacts, threads, digests. Runs locally from the mail-index npm package.
proton-bridge-mcp
MCP server "proton-bridge-mcp" as configured in Considus/proton-bridge-mcp. Launched with https://github.com/Considus/proton-bridge-mcp/releases/download/v1.2.2/proton-br.
trove-runtime
MCP server "trove-runtime" as configured in JNHFlow21/trove. Runs locally from the trove-runtime Python package.
myday
A private, local memory of what you did on your Mac — 10-minute Markdown records, searchable, and readable by your AI coding agent over MCP. Runs locally from the @abhitsian/myday npm package.
hermes-kakao-mcp
MCP server "hermes-kakao-mcp" as configured in Bum-Boo/kakaotalk-local-mcp. Runs locally from the hermes-kakao-mcp Python package.
mbox-mcp
Search local email archives (.mbox/.eml) entirely on your machine. No OAuth, no cloud. Runs locally from the mbox-mcp npm package.