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 agentmods add skills/decocms/studio/tool-scriptingnpx skills add decocms/studio --skill tool-scriptinggit clone --depth 1 https://github.com/decocms/studioWhat 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 | $0.00078 | $0.00925 |
| Opus 5 | $0.00039 | $0.00463 |
| Sonnet 5 | $0.00016 | $0.00185 |
| Haiku 4.5 | $0.00008 | $0.00093 |
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.
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. ThetypegenCLI 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 }));
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.
- 2d ago First seen · 108 lines · 78 tokens per session scan A 8f68d3f2fc94
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.
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…
refactor-module
Transform monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.
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.
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.
document-parsing
Extract readable Markdown from local Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, and text-based PDF files using the preinstalled AnyDoc runtime.
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…