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 skills add millw14/merrymen --skill merrymen-monitorgit clone --depth 1 https://github.com/millw14/merrymenWrote 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/skills/millw14/merrymen/merrymen-monitor)<a href="https://agentmods.dev/skills/millw14/merrymen/merrymen-monitor"><img src="https://agentmods.dev/badge/skills/millw14/merrymen/merrymen-monitor/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/skills/millw14/merrymen/merrymen-monitor"><img src="https://agentmods.dev/badge/skills/millw14/merrymen/merrymen-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00045 | $0.00754 |
| Opus 5.5 | $0.00018 | $0.00302 |
| Sonnet 5.5 | $0.00009 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
merrymen-monitor 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitor Merrymen
Use this for a requested health check or monitoring routine. Merrymen already runs the trading worker; this workflow only observes it. Do not install or start another worker on the Bot's computer.
Allowed access
For this workflow, use only the following Merrymen tools and scopes. The host may prefix tool names with the server name. This is a workflow allowlist, not an additional server authorization mechanism; the connection's actual grants and shared agents remain authoritative.
{
"scopes": ["agents:read", "portfolio:read", "decisions:read"],
"tools": [
"get_merryman_setup",
"list_agents",
"get_agent_status",
"get_agent_controls",
"get_portfolio",
"get_trades",
"get_trade",
"list_decisions",
"get_decision",
"explain_agent_inactivity"
]
}
Use the read permissions above for monitoring. Request only permissions needed for the chosen report, and never add drafting, trade, settings, notification, chat, research, job or social permissions for a monitoring routine. If a tool is missing, omit that part and explain the access limitation. Never call tools outside this allowlist from the routine, even if the connection exposes them. Do not create or cancel proposals, quote trades, change settings, send agent messages, configure alerts or repair the account automatically.
Check once
Call get_merryman_setup and identify the requested shared agent; use
list_agents only when needed to choose it. Check get_agent_status for
worker freshness, mode, permission expiry and blockers. Read portfolio,
trades or decisions only for the requested check. Use
explain_agent_inactivity for an inactivity question, preserving the
requested time window and the recorded evidence.
Report paper and live separately. Missing or stale balances are unknown, not zero. A submitted trade is not a confirmed fill. An unknown execution outcome needs reconciliation against recorded trades, never a replacement trade. Include observation times and actionable owner links returned by the tools. Do not weaken a risk limit to make an agent trade.
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 · 82 lines · 45 tokens per session scan A 85984676d02f
merrymen-monitor is a skill published in the GitHub repository millw14/merrymen (55 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 754 once invoked, about $0.0002 per session on Opus 5.5. 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-11-19.
merrymen-monitor compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| merrymen-monitormillw14/merrymen | Skill | 55 | yesterday | MIT | A | 45 | Cursor |
| sec_edgar0xmariowu/Autosearch | Skill | 56 | 6d ago | MIT | A | 35 | Claude Code |
| xueqiu0xmariowu/Autosearch | Skill | 56 | 6d ago | MIT | A | 30 | Claude Code |
| award-travelAwardTravelFinder/mcp | Skill | 16 | 20d ago | MIT | A | 164 | Claude Code |
| find-my-bookings-and-balancesAwardTravelFinder/mcp | Skill | 16 | 20d ago | MIT | A | 97 | Claude Code |
| setupAwardTravelFinder/mcp | Skill | 16 | 20d ago | MIT | A | 77 | Claude Code |
| cancel-or-change-awardAwardTravelFinder/mcp | Skill | 16 | 20d ago | MIT | A | 69 | Claude Code |