custom-tools

A way to add your own JavaScript functions as callable tools for individual coding agents. Each agent can have its own set of workspace-based tools.

In plain words
What is it for?
Register workspace JavaScript files, such as a tool that searches Jira issues, and make them available to a selected agent.
Why use it?
It lets different agents use only the extra tools they need, instead of giving every agent the same tool set. This keeps agent capabilities separated.

Agent

Install

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.

agentmods
npx agentmods add agents/algopian/chromeclaw/custom-tools
Clone the repo
git clone --depth 1 https://github.com/algopian/chromeclaw
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 672 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
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 $0.00000 $0.00672
Opus 5 $0.00000 $0.00336
Sonnet 5 $0.00000 $0.00134
Haiku 4.5 $0.00000 $0.00067

Measured 2d ago against content hash 5434e315301f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

custom-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 2d 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

const response = await fetch('https://your-jira.atlassian.net/rest/api/3/search', { method: 'POST',
docs/agents/custom-tools.md · 89 lines

How it starts

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

Custom Agent Tools

Each agent can have custom JavaScript tools registered from workspace files. These tools are only available to the agent they're registered with, allowing different agents to have different capabilities.

Overview

Custom tools extend an agent's built-in tool set with your own JavaScript functions. They use @tool metadata comments for definition and run in the JS sandbox.

For full documentation on the @tool format, see Custom Tools.

Per-agent registration

Custom tools are stored in each agent's customTools array. To register a tool for a specific agent:

  1. Create a workspace file with @tool metadata
  2. Register it using the execute_javascript tool with action: "register"
  3. The tool is added to the active agent's tool set

When you switch agents, the available custom tools change to match the new agent's registrations.

Example: API integration tool

Create a workspace file jira-search.js:

// @tool jira_search
// @description Search Jira issues by JQL query
// @param jql string "JQL query string"
// @param maxResults number "Maximum results to return"

const response = await fetch('https://your-jira.atlassian.net/rest/api/3/search', {
  method: 'POST',
  headers: {
    'Authorization': `Basic ${btoa('[email protected]:YOUR_API_TOKEN')}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    jql: args.jql,
    maxResults: args.maxResults || 10,
    fields: ['summary', 'status', 'assignee', 'priority']
  })
});

const data = await response.json();
return data.issues.map(i => ({
  key: i.key,
  summary: i.fields.summary,
  status: i.fields.status.name,
  assignee: i.fields.assignee?.displayName || 'Unassigned'
}));

Register it:

Register jira-search.js as a custom tool for this agent

Now the agent can search Jira:

Search Jira for open bugs assigned to me

Managing custom tools

  • List: Use the list workspace tool to see all files, including registered tools
  • Update: Edit the workspace file — changes take effect on next use
  • Unregister: Use execute_javascript with action: "unregister"
  • Per-agent: Switch agents to manage tools for different agents

Read the full file on GitHub · 89 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. 2d ago First seen · 89 lines · 0 tokens per session scan B 5434e315301f

Subscribe to this mod's changes

custom-tools is an agent published in the GitHub repository algopian/chromeclaw (197 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 672 tokens. A static security scan graded it B with 1 finding (sends data to an external url). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens