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 tallclub/matimo --skill tool-discoverygit clone --depth 1 https://github.com/tallclub/matimoWrote 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/tallclub/matimo/tool-discovery)<a href="https://agentmods.dev/skills/tallclub/matimo/tool-discovery"><img src="https://agentmods.dev/badge/skills/tallclub/matimo/tool-discovery/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/tallclub/matimo/tool-discovery"><img src="https://agentmods.dev/badge/skills/tallclub/matimo/tool-discovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 168 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 206 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Excessive Agency · line 175 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Data Exfiltration · line 187 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00041 | $0.01736 |
| Opus 5.5 | $0.00016 | $0.00694 |
| Sonnet 5.5 | $0.00008 | $0.00347 |
| Haiku 4.5 | $0.00004 | $0.00174 |
Grade A, and why
tool-discovery 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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tool Discovery: Finding and Inspecting Tools
This skill teaches you how to find the tools you can use before you write a new one. Reusing an existing, approved tool is always faster and safer than creating one.
Where Tools Come From
- Core tools — shipped with Matimo:
calculator,web,read,search,edit,executeand others, plus thematimo_*meta-tools that manage tools and skills. - Provider tools — from installed provider packages (Slack, GitHub, Gmail, Notion, HubSpot, and more), loaded by the developer.
- Tools created by agents — written with
matimo_create_toolinto a directory the developer chose. They start as drafts and run only after a human approves them.
Which Tool Answers Which Question
| Question | Tool |
|---|---|
| Is there already a tool for this? | matimo_search_tools |
| What exactly does tool X do and take? | matimo_get_tool |
| Which tools have agents created here? | matimo_list_user_tools |
| Can tool X run yet? | matimo_get_tool_status |
| Is there guidance for this kind of task? | matimo_search_skills, matimo_list_skills |
matimo_search_tools — search everything that is loaded
matimo_search_tools(query: "slack message", limit: 5)
→ {
"results": [
{ "name": "slack_send_channel_message", "description": "...", "version": "1.0.0", "tags": ["slack", "messaging"], "riskLevel": "medium" }
],
"total": 1,
"query": "slack message"
}
- Matches the query against tool names, descriptions and tags.
- Searches every loaded tool — core, provider and approved agent-created tools.
- An empty result means nothing loaded matches: try other words before deciding to create a tool.
matimo_get_tool — read one tool's definition
matimo_get_tool(name: "weather_lookup", tool_dir: "<directory>")
→ { "found": true, "name": "weather_lookup", "yaml_content": "name: weather_lookup\n...", "definition": { ... }, "message": "..." }
Use it to see a tool's parameters before calling it, or to start a new tool from an existing one.
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 Changed · -322 lines · +8 tokens per session 862f0df256eb
- 2mo ago First seen · 499 lines · 33 tokens per session scan A 9ba996e3737e
tool-discovery is a skill published in the GitHub repository tallclub/matimo (18 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 1,736 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-08-30.
tool-discovery compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| tool-discoverytallclub/matimo | Skill | 18 | yesterday | MIT | A | 41 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 103 | Claude Code |