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/bartekrutkowski/watchgoose-mcpWrote 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/plugins/bartekrutkowski/watchgoose-mcp/watchgoose-monitoring)<a href="https://agentmods.dev/plugins/bartekrutkowski/watchgoose-mcp/watchgoose-monitoring"><img src="https://agentmods.dev/badge/plugins/bartekrutkowski/watchgoose-mcp/watchgoose-monitoring/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/plugins/bartekrutkowski/watchgoose-mcp/watchgoose-monitoring"><img src="https://agentmods.dev/badge/plugins/bartekrutkowski/watchgoose-mcp/watchgoose-monitoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
watchgoose-monitoring 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
{
"name": "watchgoose-monitoring",
"displayName": "Watchgoose Monitoring",
"version": "1.1.2",
"description": "Audit cron and scheduled-job monitoring coverage, set up Watchgoose checks for one job or a batch, review monitoring health and triage missed runs.",
"author": { "name": "Watchgoose.com", "url": "https://watchgoose.com/" },
"homepage": "https://watchgoose.com/docs/mcp/",
"documentationUrl": "https://watchgoose.com/docs/mcp/",
"repository": "https://github.com/bartekrutkowski/watchgoose-mcp",
"license": "MIT",
"keywords": [
"cron",
"cronjobs",
"jobs",
"scheduled",
"scheduled-jobs",
"recurring",
"backups",
"monitoring",
"systemd",
"systemd-timers",
"kubernetes",
"kubernetes-cronjobs",
"heartbeat",
"watchgoose"
],
"icon": "./.claude-plugin/icon.png",
"privacyPolicyUrl": "https://watchgoose.com/legal/privacy/",
"termsOfServiceUrl": "https://watchgoose.com/legal/terms/",
"supportUrl": "https://watchgoose.com/about/#about-faq-title"
}
What it installs
The manifest is a name and a version. 5 skills travel with it, and installing the plugin installs all of them — 219 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +5 lines 07accc48e252
- 2d ago Changed · +15 lines 95774ec5e704
- 4d ago First seen · 12 lines scan A e0df3cea2ec3
watchgoose-monitoring is a plugin published in the GitHub repository bartekrutkowski/watchgoose-mcp (1 stars, last pushed yesterday), 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 A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-12.
Other plugins, from other repositories
pm-agentops
Operate AI agents and LLM features in production: prompt regression suites, model migration plans, context-engineering reviews, agent incident postmortems, and observability specs — plus the pm-ai evaluation and cost skills they build on.
whimsical
Whimsical's official MCP server. Create and edit boards, docs, flowcharts, mind maps, sequence diagrams, wireframes, tables and sticky notes, then read, search and comment on anything already in the workspace. OAuth 2.1, no API key; a free Whimsical account can use every tool.
ai-news-hq
An AI-news crew (scout, analyst, editor) that tracks the field via web search and ships a ranked briefing on a cadence.
pict-test-designer
Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for any piece of requirements or code. Analyzes inputs, generates PICT models with parameters, values, and constraints for valid scenarios using pairwise testing. Outputs the PICT model, markdown table of test cases, and expected…
prism
PRISM — structured, multi-session, multi-vendor LLM-orchestrated audit & research framework. Lean always-loaded core + on-demand reference bundles.
multai
MultAI — Submit research prompts to 7 AI platforms simultaneously (Claude.ai, ChatGPT, Copilot, Perplexity, Grok, DeepSeek, Gemini), synthesize results, maintain capability comparison matrices, and produce landscape reports — all from Claude Code.