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/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/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/wulfgardr/work-assistant/work-assistant"><img src="https://agentmods.dev/badge/mcp/wulfgardr/work-assistant/work-assistant.svg" alt="Reviewed on agentmods" width="80" 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 1mo 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.
- 1mo ago First seen · 8 lines scan A 88b5012a3834
work-assistant is an MCP server published in the GitHub repository Wulfgardr/work-assistant (1 stars, last pushed 7d 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
trove-runtime
MCP server "trove-runtime" as configured in JNHFlow21/trove. Runs locally from the trove-runtime Python 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.
agent-memory-control-plane
MCP server "agent-memory-control-plane" as configured in AlekseiUL/agent-memory-control-plane. Runs locally from the agent-memory-control-plane Python package.
lians_memory
MCP server "liansmemory" as configured in Lians-ai/Lians. Launched with lians-memory-mcp. Needs 11 environment variables to run.
agent-job-search
MCP server "agent-job-search" as configured in russeell/jobfindsme. Runs locally from the agent-job-search Python package.
lians
Correct, temporal, and auditable memory infrastructure for AI agents. Runs locally from the lians-sdk Python package. Needs 5 environment variables to run.