tool-scripting

A way to run an organisation's available MCP tools from shell scripts. MCP tools are connected services that an agent can call; this add-on provides their schemas and a command-line caller.

In plain words
What is it for?
Use it for repeated calls to the same tool, such as processing many files, rows, or items. It supports listing available tools, checking one tool's input format, and running one-off or scripted calls.
Why use it?
It avoids making repeated tool calls one at a time and gives bulk results in a file that can be inspected afterward. It also shows how to discover a tool's required inputs.

Skill for Claude CodeCodex

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 skills/decocms/studio/tool-scripting
Any agent
npx skills add decocms/studio --skill tool-scripting
Clone the repo
git clone --depth 1 https://github.com/decocms/studio

Made for: Claude Code, Codex.

Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 925 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00078 $0.00925
Opus 5 $0.00039 $0.00463
Sonnet 5 $0.00016 $0.00185
Haiku 4.5 $0.00008 $0.00093

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

Security

Grade A, and why

tool-scripting 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 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.

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.

packages/sandbox/image/skills/tool-scripting/SKILL.md · 108 lines

How it starts

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

tool-scripting — call org tools from scripts

The workspace carries a materialized catalog of the org's tools:

  • .deco/tools/<TOOL>.json — one JSON Schema per tool: { name, description, inputSchema, outputSchema }
  • .deco/tools/.endpoint.json — the run's pre-authenticated MCP endpoint. The typegen CLI and client discover it automatically (walking up from cwd) — no flags, keys, or env needed. The daemon refreshes it; a reconnect picks up new credentials.

Discover tools (cheap)

Browse the catalog from disk instead of loading every schema into context:

ls .deco/tools/
cat .deco/tools/SEND_EMAIL.json

or typegen tools (list names + descriptions) / typegen tools SEND_EMAIL (one tool's full schema).

One-off call from the shell

typegen call SEND_EMAIL '{"to":"[email protected]","subject":"hi"}'

Prints the tool's structured output as JSON; non-zero exit and a message on stderr on failure. If typegen is not on PATH, use bunx @decocms/typegen call ....

Bulk calls — write a script

For N calls (a tool per row/file/item), never loop through your own tool-calling — write a script, run it, read back the summary. Results belong in a file, not in your context.

Set up a scratch project so the user's repo stays untouched. Cloud sandboxes carry the typegen package built from the same Studio revision; Desktop falls back to the published package. Then run from the repo root (endpoint discovery walks up from cwd):

mkdir -p /tmp/toolrun && cd /tmp/toolrun
if [ -f /opt/sandbox-daemon/typegen.tgz ]; then
  bun add /opt/sandbox-daemon/typegen.tgz
else
  bun add @decocms/typegen
fi
cd - && bun run /tmp/toolrun/bulk.ts
// /tmp/toolrun/bulk.ts
import { createStudioClient } from "@decocms/typegen";

const client = createStudioClient(); // discovers .deco/tools/.endpoint.json
const rows: { email: string }[] = JSON.parse(
  await Bun.file("input.json").text(),
);

const out = Bun.file("results.jsonl").writer();
let ok = 0;
let failed = 0;
for (const [i, row] of rows.entries()) {
  try {
    const result = await client.SEND_EMAIL({ to: row.email, subject: "hi" });
    out.write(`${JSON.stringify({ i, ok: true, result })}\n`);
    ok++;
  } catch (err) {
    out.write(`${JSON.stringify({ i, ok: false, error: String(err) })}\n`);
    failed++;
  }
  if (i % 25 === 0) console.error(`progress ${i}/${rows.length}`);
}
out.end();
await client.close();
console.log(JSON.stringify({ ok, failed, total: rows.length }));

Read the full file on GitHub · 108 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 · 108 lines · 78 tokens per session scan A 8f68d3f2fc94

Subscribe to this mod's changes

tool-scripting is a skill published in the GitHub repository decocms/studio (401 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 925 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

opengeni

Use when editing, operating, extending, documenting, or debugging the OpenGeni source repository or deployment: architecture, sessions/events, worker orchestration, sandbox backends, files/storage, tools/MCP, scheduling, configuration, and deployment. For a customer product that consumes a standalone OpenGeni…

Cloudgeni-ai/opengeni · 81 tokens

refactor-module

Transform monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.

Cloudgeni-ai/opengeni · 28 tokens

terraform-search-import

Discover existing cloud resources using Terraform Search queries and bulk import them into Terraform management. Use when bringing unmanaged infrastructure under Terraform control, auditing cloud resources, or migrating to IaC.

Cloudgeni-ai/opengeni · 39 tokens

checkov

Use Checkov to scan Terraform and infrastructure-as-code repositories for policy violations, explain findings, choose safe fixes, rerun scans, and prepare pull requests with remediations.

Cloudgeni-ai/opengeni · 38 tokens

document-parsing

Extract readable Markdown from local Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, and text-based PDF files using the preinstalled AnyDoc runtime.

Cloudgeni-ai/opengeni · 39 tokens

opengeni-client

Use when an external product, coding agent, CLI, backend, or automation uses a standalone OpenGeni deployment through @opengeni/sdk or @opengeni/react. Covers choosing between a stock-UI handoff, a headless product integration, embedded React session surfaces, or the optional workbench; tenant-safe proxy boundaries…

Cloudgeni-ai/opengeni · 114 tokens