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 jpoutrin/product-forge --skill agent-toolsgit clone --depth 1 https://github.com/jpoutrin/product-forgeWrote 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/jpoutrin/product-forge/agent-tools)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/agent-tools"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/agent-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/jpoutrin/product-forge/agent-tools"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/agent-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.00032 | $0.01903 |
| Opus 5.5 | $0.00013 | $0.00761 |
| Sonnet 5.5 | $0.00006 | $0.00381 |
| Haiku 4.5 | $0.00003 | $0.00190 |
Grade B, and why
agent-tools scanned grade B 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 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
### Allow All Tools from a Server Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- For URL restrictions, prefer `WebFetch(domain:...)` over `Bash(curl:*)` How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Tools Reference
Configure tool permissions when launching parallel Claude Code agents.
Available Tools
| Tool | Description | Use Case |
|---|---|---|
Read |
Read files | Always needed for context |
Write |
Create new files | Creating new code files |
Edit |
Modify existing files | Updating existing code |
Bash |
Execute shell commands | Running tests, builds, git |
Glob |
Find files by pattern | File discovery |
Grep |
Search file contents | Code search |
WebFetch |
Fetch web content | Documentation lookup |
WebSearch |
Search the web | Research |
TodoWrite |
Manage task lists | Progress tracking |
Task |
Launch sub-agents | Delegation |
NotebookEdit |
Edit Jupyter notebooks | Data science |
mcp__<server> |
MCP server tools | External integrations |
CLI Syntax
Each tool is a separate quoted argument:
claude --allowedTools "Tool1" "Tool2" "Tool3(...)" --print "prompt"
Example with multiple tools:
claude --allowedTools "Read" "Edit" "Bash(pytest:*)" --print "implement feature"
Path-Specific Restrictions
Restrict file operations to specific directories using gitignore-style patterns.
Path Pattern Syntax
| Pattern | Meaning | Example |
|---|---|---|
//path |
Absolute filesystem path | Edit(//Users/alice/src/**) |
~/path |
Home directory relative | Read(~/.zshrc) |
/path |
Relative to settings file | Edit(/src/**/*.ts) |
path |
Relative to current directory | Read(src/**) |
Examples
# Allow editing only in src/ directory
claude --allowedTools "Edit(/src/**)" --print "..."
# Allow editing TypeScript files only
claude --allowedTools "Edit(/src/**/*.ts)" --print "..."
# Multiple path restrictions
claude --allowedTools "Read" "Edit(/apps/users/**)" "Edit(/tests/**)" --print "..."
# Absolute path restriction
claude --allowedTools "Edit(//tmp/scratch.txt)" --print "..."
Bash Command Restrictions
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 First seen · 260 lines · 32 tokens per session scan B 51351dbc64d5
agent-tools is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 1,903 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 2 findings (unrestricted tool access, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…