tools

tools is a skill for Claude Code from bethanychamberlain/claude-skills-librechat. It costs 64 tokens per session (1,702 once invoked), scanned B, original, MIT.

LibreChat tool-configuration guidance for agent capabilities such as code execution, web search, image generation, weather, document search, artifacts, and OCR. An agent is a configured AI assistant that can use selected tools.

In plain words
What is it for?
Use it to enable or disable tools, configure their providers, combine capabilities for an agent, and verify the resulting setup.
Why use it?
It helps administrators choose and enable the tools an agent needs without guessing which environment variables or YAML settings to change.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the librechat-data plugin — 2 skills shipped together

Good fit Use it to enable or disable tools, configure their providers, combine capabilities for an agent, and verify the resulting setup.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add bethanychamberlain/claude-skills-librechat
Claude Code
/plugin install librechat-data

Made for: Claude Code.

Or install librechat-data, the plugin that ships this one along with the rest of its 2 skills.

Wrote 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.

agentmods badge for tools

README.md
[![agentmods](https://agentmods.dev/badge/skills/bethanychamberlain/claude-skills-librechat/tools/github.svg)](https://agentmods.dev/skills/bethanychamberlain/claude-skills-librechat/tools)
Your own site
<a href="https://agentmods.dev/skills/bethanychamberlain/claude-skills-librechat/tools"><img src="https://agentmods.dev/badge/skills/bethanychamberlain/claude-skills-librechat/tools/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.

agentmods 80×15 button for tools

Your own site · 80×15
<a href="https://agentmods.dev/skills/bethanychamberlain/claude-skills-librechat/tools"><img src="https://agentmods.dev/badge/skills/bethanychamberlain/claude-skills-librechat/tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,702 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.01702
Opus 5 $0.00032 $0.00851
Sonnet 5 $0.00013 $0.00340
Haiku 4.5 $0.00006 $0.00170

Measured 9d ago against content hash a2f0c6b81093, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade B, and why

tools scanned grade B with 1 finding 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.

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

1. **Code interpreter + open registration** → "Code interpreter is enabled and registration is open. Any registered user can execute arbitrary code in the sandbox. While the sandbox is isolated, verify this is intentiona
librechat-data/skills/tools/SKILL.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

LibreChat Tools

You are an expert in LibreChat's tool ecosystem. Your goal is to help admins enable, configure, and combine the right tools for their agents' needs.

Before Starting

Check for context first: If librechat-context.md exists in the current working directory, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

If librechat-context.md does not exist, ask the user:

  1. What LibreChat version are you running?
  2. How is it deployed? (Docker local / Docker remote / cloud / Kubernetes)
  3. What model providers are configured?

Then offer: "Would you like me to save this as librechat-context.md so you don't have to answer these again?" If they say yes, also remind them to add librechat-context.md to .gitignore.

How This Skill Works

Mode 1: Enable a Specific Tool

When the user wants to turn on a particular capability.

  1. Identify which tool they want
  2. Load the relevant reference doc (see table below)
  3. Provide exact config: .env variables + YAML changes
  4. Show restart command and verification steps

Mode 2: Design a Tool Loadout

When the user describes what an agent should do, and needs tool recommendations.

  1. Load ${CLAUDE_PLUGIN_ROOT}/references/tools-overview.md for the full capability matrix
  2. Load ${CLAUDE_PLUGIN_ROOT}/templates/tools-comparison.md for "I want my agent to..." recommendations
  3. Recommend the right combination of tools based on:
    • Agent purpose and audience
    • Budget (some tools require paid APIs)
    • Privacy requirements (some send data externally)
    • Self-hosting preference
  4. Produce complete config for all recommended tools

Mode 3: Debug Tool Issues

When a tool is not working as expected.

  1. Identify which tool is failing
  2. Common checks:
    • Is the capability enabled in YAML? (endpoints.agents.capabilities)
    • Is the capability toggled ON for this specific agent?
    • Are required .env variables set?
    • Is the external service reachable?
  3. Load the relevant reference doc for tool-specific diagnostics
  4. Provide exact fix with verification

Read the full file on GitHub · 146 lines

Changes

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.

  1. 9d ago First seen · 146 lines · 64 tokens per session scan B a2f0c6b81093

Subscribe to this mod's changes

tools is a skill published in the GitHub repository bethanychamberlain/claude-skills-librechat (3 stars, last pushed 5mo ago), licensed MIT. It adds 64 tokens to every session and 1,702 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

TEMPLATE

../../../agents/personas/TEMPLATE.md.

alirezarezvani/claude-skills · 0 tokens

world-model-diagnostic

Twenty-minute diagnostic mapping a team to a world-model paradigm (vector DB, structured ontology, signal-fidelity). Use when you say "run the world model diagnostic", "audit our world model", "which world model architecture fits us", or "audit where we automate judgment". Use for AI readiness assessments and…

rjmurillo/ai-agents · 94 tokens

observability

Use when you say query agent logs, find slow tool calls, or show agent errors. Query and analyze agent JSONL event logs for debugging, performance analysis, and decision tracing.

rjmurillo/ai-agents · 42 tokens

avoiding-manufactured-work

Detect and stop manufactured work after a deliverable appears done, and classify a post-completion finding into the four contract classes builder-ethos.md delegates here. Use when a worker has produced a plan, issue, PR, backlog item, research artifact, or follow-up task and you need to verify it was demanded by a…

rjmurillo/ai-agents · 88 tokens

ai-agents-change-control

Change control for this repo. Classify a change (docs-only, investigation-only, code, plugin content, hook, workflow, ADR governance), map each class to the gates it triggers, and hold the non-negotiables with the incident behind each rule. Use when you say classify this change, what gates does this change trigger…

rjmurillo/ai-agents · 119 tokens

business-strategy

Route a founder problem to the right business framework, then load that framework on demand. Distills 14 business books (customer discovery, positioning, pricing, sales, growth, persuasion) into scored, decision-tree skills. Use when you say diagnose my business problem, what framework applies, how do I validate…

rjmurillo/ai-agents · 104 tokens