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 hajekim/agentic-design-patterns-skills --skill tool-usegit clone --depth 1 https://github.com/hajekim/agentic-design-patterns-skillsWrote 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/hajekim/agentic-design-patterns-skills/tool-use)<a href="https://agentmods.dev/skills/hajekim/agentic-design-patterns-skills/tool-use"><img src="https://agentmods.dev/badge/skills/hajekim/agentic-design-patterns-skills/tool-use/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/hajekim/agentic-design-patterns-skills/tool-use"><img src="https://agentmods.dev/badge/skills/hajekim/agentic-design-patterns-skills/tool-use.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.00365 | $0.03770 |
| Opus 5 | $0.00182 | $0.01885 |
| Sonnet 5 | $0.00073 | $0.00754 |
| Haiku 4.5 | $0.00036 | $0.00377 |
Grade A, and why
tool-use scanned grade A with 2 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = requests.get(endpoint, params=params, timeout=10) Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
result = subprocess.run( Copies of this mod
1 near-identical copy found in the catalogue:
- tool-use — 100% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tool Use Pattern
Overview
The Tool Use Pattern extends an agent's capabilities beyond pure language generation by enabling it to interact with external systems — APIs, databases, search engines, code executors, and more. The agent reasons about which tool to call, invokes it with appropriate parameters, processes the returned data, and integrates the results into its response.
Core Principle: Extend the agent's reach — let it act in the world, not just reason about it.
When This Skill Applies
Activate this pattern when:
- The agent needs real-time or external data (weather, stock prices, news)
- Tasks require computation, code execution, or mathematical verification
- Document retrieval and RAG (Retrieval-Augmented Generation) is needed
- The agent must persist state (write to databases, files, memory stores)
- Actions must be taken in the world (send email, create calendar events, trigger workflows)
- The agent needs to verify its reasoning with factual lookups
Rule of thumb: If the task requires information or capabilities beyond the model's training data or inherent abilities — use tools.
DEFINE → PLAN → ACTION Workflow
DEFINE
Map the tool requirements:
- What external data or capabilities does the agent need?
- What tools exist or need to be built to provide those capabilities?
- What are the input/output schemas for each tool?
- What are the failure modes and how should they be handled?
PLAN
Design the tool integration:
- Define each tool with a clear name, description, and parameter schema
- Write tool descriptions that help the LLM understand when and how to use each tool
- Design the tool selection logic (LLM-driven function calling vs. rule-based)
- Plan error handling for API failures, timeouts, and unexpected responses
- Consider tool chaining — sequential tool calls where outputs feed subsequent calls
ACTION
Implement tool-enabled agents:
- Register tools with the LLM using the framework's function calling interface
- Implement each tool function with proper input validation and error handling
- Let the LLM determine when and how to call tools based on user intent
- Process tool results and integrate them into the agent's response
- Log tool calls for observability and debugging
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.
- 9d ago First seen · 437 lines · 365 tokens per session scan A 22f272918ace
tool-use is a skill published in the GitHub repository hajekim/agentic-design-patterns-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 365 tokens to every session and 3,770 once invoked, about $0.0018 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
impact-audit
Blast radius of a change you have not made yet -- traces a symbol across federated repositories, splits impact per repo, and reports what must ship together.
onboard-repo
Index an unfamiliar codebase into the knowledge graph, then produce a first orientation map -- entry points, most-depended-upon modules, hotspots, test topology.
prompt-optimizer
Analyze raw prompts, identify intent and gaps, match ECC components (skills/commands/agents/hooks), and output a ready-to-paste optimized prompt. Advisory role only — never executes the task itself. TRIGGER when: user says "optimize prompt", "improve my prompt", "how to write a prompt for", "help me prompt", "rewrite…
openclaw-persona-forge
A persona-design guide for OpenClaw agents, including their identity, personality, boundaries, names, and avatar prompts. OpenClaw is the specific agent platform this guide targets.
gemini-api
Google Gemini API patterns for Python and TypeScript. Covers content generation, streaming, tool use (function calling), vision, system instructions, context caching, batch requests, and agent workflows. Use when building applications with the Gemini API or Google Generative AI SDKs.
jira-integration
Use this skill when retrieving Jira tickets, analyzing requirements, updating ticket status, adding comments, or transitioning issues. Provides Jira API patterns via MCP or direct REST calls.