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 takeshy/obsidian-llm-hub --skill add-toolgit clone --depth 1 https://github.com/takeshy/obsidian-llm-hubWrote 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/takeshy/obsidian-llm-hub/add-tool)<a href="https://agentmods.dev/skills/takeshy/obsidian-llm-hub/add-tool"><img src="https://agentmods.dev/badge/skills/takeshy/obsidian-llm-hub/add-tool/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/takeshy/obsidian-llm-hub/add-tool"><img src="https://agentmods.dev/badge/skills/takeshy/obsidian-llm-hub/add-tool.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.00032 | $0.00474 |
| Opus 5 | $0.00016 | $0.00237 |
| Sonnet 5 | $0.00006 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
add-tool 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 12d 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.
This is a copy
100% identical to add-tool — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Add New Function Calling Tool
Add a new function calling tool called $ARGUMENTS to the Gemini chat integration.
Required File Changes
1. src/core/tools.ts
- Add
ToolDefinitionto the appropriate tools array (read/write/delete) - Define
name,description, andparametersschema - Property types:
STRING,BOOLEAN,INTEGER,ARRAY,OBJECT - Add to
getEnabledTools()logic if it needs conditional enabling
2. src/vault/toolExecutor.ts
- Add
caseinexecuteToolCall()switch for the new tool name - Implement the execution logic (typically calling methods from
notes.tsorsearch.ts)
3. src/vault/notes.ts or src/vault/search.ts (if needed)
- Add the underlying vault operation method if it doesn't exist yet
- Use
app.vaultfor file operations,app.workspacefor UI operations
4. System prompt in src/ui/components/Chat.tsx
- Update the system prompt to mention the new tool's capabilities
- This helps the model know when to use the tool
Tool Design Guidelines
- Safe editing: Use
propose_editpattern (apply changes, backup original, user confirms) - Read-only tools: Always enabled; add to read tools array
- Write tools: Gated by
allowWriteoption - Delete tools: Gated by
allowDeleteoption (opt-in) - Naming: Use
snake_case(e.g.,read_note,create_folder) - Results: Return structured objects; large results will be truncated to 500 chars in tracing
Verification
- Run
npm run lint - Run
npm run build - Verify the tool appears in enabled tools based on its category
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.
- 12d ago First seen · 47 lines · 32 tokens per session scan A c779b7a6d6c4
add-tool is a skill published in the GitHub repository takeshy/obsidian-llm-hub (34 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 474 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to add-tool, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
using-ccproxy-api
Guides users through ccproxy as an OpenAI-compatible and Anthropic-compatible LLM API server with SDK integration, OAuth authentication, sentinel key substitution, model routing, and troubleshooting. Use when installing ccproxy, configuring SDK clients (Anthropic, OpenAI, LiteLLM, Agent SDK) against ccproxy, setting…
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
afm
Maintain and extend AFM (maclocal-api), a Swift OpenAI-compatible local LLM server and CLI for Apple Foundation Models, MLX models, API gateway proxying, and Vision OCR. Use when working on AFM CLI commands (afm, afm mlx, afm vision), OpenAI /v1/chat/completions and /v1/models behavior, streaming SSE, tool-calling…
api-services
API reference for built-in service providers (LLM, Speech, Graph). Use when looking up service interfaces, provider capabilities, or integration patterns.