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 lttr/claude-marketplace --skill list-builtin-toolsgit clone --depth 1 https://github.com/lttr/claude-marketplaceWrote 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/lttr/claude-marketplace/list-builtin-tools)<a href="https://agentmods.dev/skills/lttr/claude-marketplace/list-builtin-tools"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/list-builtin-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.
<a href="https://agentmods.dev/skills/lttr/claude-marketplace/list-builtin-tools"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/list-builtin-tools.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.00012 | $0.00342 |
| Opus 5 | $0.00006 | $0.00171 |
| Sonnet 5 | $0.00002 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade D, and why
list:builtin-tools scanned grade D 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 11d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. Read the `permissions.deny` array from each settings file that applies, in order: `~/.claude/settings.json`, `.claude/settings.json`, `.claude/settings.local.json`. Collect bare tool-name entries (e.g. `NotebookEdit`) Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
1. Read the `permissions.deny` array from each settings file that applies, in order: `~/.claude/settings.json`, `.claude/settings.json`, `.claude/settings.local.json`. Collect bare tool-name entries (e.g. `NotebookEdit`) What it actually says
Context
Claude Code has a set of built-in tools that are always available, separate from MCP server tools. Users may want to see what built-in tools are available for reference.
Tools denied via permissions.deny in settings are removed from the session entirely — they never appear in the tool list, not even as deferred tools. So the live tool list alone under-reports what the harness ships: a denied tool looks identical to a tool that doesn't exist. Read the settings files to tell the two apart.
Your task
- Read the
permissions.denyarray from each settings file that applies, in order:~/.claude/settings.json,.claude/settings.json,.claude/settings.local.json. Collect bare tool-name entries (e.g.NotebookEdit); ignore scoped ones likeBash(rm -rf /*:*), which gate arguments rather than the tool. - List all built-in Claude Code tools (excluding MCP tools that start with
mcp__) — both the ones available this session and the ones denied by those settings.
For each tool, provide:
- Tool name in backticks
- Brief description (one line)
— disabled (deny: <settings file>)suffix if it was denied
Organize by category:
- File Operations
- Execution & Shell
- Web Access
- Task Management
- Integration
Deferred tools (schemas loaded on demand via ToolSearch) are available — list them normally, not as disabled.
Use compact format with minimal formatting.
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.
- 11d ago First seen · 35 lines · 12 tokens per session scan D 0a847b828f56
list:builtin-tools is a skill published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 342 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
stream-chain
Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows.
hook-factory
Generate production-ready Claude Code hooks with interactive Q&A, automated installation, and enhanced validation. Supports 10 templates across 7 event types for comprehensive workflow automation.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
development
An index of programming guidance for Python, Go, Rust, TypeScript, Java, C++, and shell scripting.