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 ANAMIZED/YodMCP --skill safe-tool-usegit clone --depth 1 https://github.com/ANAMIZED/YodMCPWrote 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/anamized/yodmcp/safe-tool-use)<a href="https://agentmods.dev/skills/anamized/yodmcp/safe-tool-use"><img src="https://agentmods.dev/badge/skills/anamized/yodmcp/safe-tool-use.svg" alt="Measured on agentmods" 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.00019 | $0.00078 |
| Opus 5 | $0.00010 | $0.00039 |
| Sonnet 5 | $0.00004 | $0.00016 |
| Haiku 4.5 | $0.00002 | $0.00008 |
Grade A, and why
safe-tool-use 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 7d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 7d ago First seen · 13 lines · 19 tokens per session scan A 0432e5f695ec
safe-tool-use is a skill published in the GitHub repository ANAMIZED/YodMCP (1 stars, last pushed 11d ago), with no licence file. It adds 19 tokens to every session and 78 once invoked, about $0.0001 per session on Opus 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-08-31.
Other skills, from other repositories
governance-hotl
OpenMesha governance — fail-closed policy, HOTL for irreversible actions, audit log inspection. Use when reviewing denials, escalations, or audit trails.
governance-audit
Inspect Server OS policy decisions, capability grants, and the audit log.
multi-agent-workflow
Orchestrate sequential multi-agent workflows under a shared budget on OpenMesha. Use when a goal needs planner/researcher/worker roles or council-style decomposition.
server-os
Autonomous Agentic Operating System — agents as first-class processes with cost control, governance, observability, MCP, SDK, CLI, and skills. Fail-closed. Use when building or operating agent runtimes that need budgets, capabilities, and verifiable end-to-end checks.
multi-agent-workflow
Orchestrate improver → evaluator → council under LRSI gates.
agentfence
Apply OpenMesha two-layer AgentFence (ingest scan + act gate) and HOTL escalation. Use when reviewing untrusted tool output, inbound messages, or irreversible/money-moving actions.