tools

A set of rules for adding tools to a TypeScript project, including how tools declare their side effects and risk level.

In plain words
What is it for?
Use it when registering tools, defining whether they read, write, use the network, or execute commands, handling errors, and enforcing filesystem and shell safety.
Why use it?
It helps keep tool actions behind permission checks, restrict filesystem paths, classify shell commands, and prevent critical-risk bypasses.

Cursor rule for Cursor

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 rules/hoangsonww/forge-agentic-coding-cli/tools
Clone the repo
git clone --depth 1 https://github.com/hoangsonww/Forge-Agentic-Coding-CLI

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 197 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.00000 $0.00197
Opus 5 $0.00000 $0.00098
Sonnet 5 $0.00000 $0.00039
Haiku 4.5 $0.00000 $0.00020

Measured yesterday against content hash 615d18992780, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tools 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 yesterday.

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.

.cursor/rules/tools.mdc · 22 lines

What it actually says

Tool authoring rules

  • Every new tool registers in src/tools/registry.ts.
  • Tool schemas must declare sideEffect (none|read|write|network|exec) and risk (low|medium|high|critical). These drive the permission classifier — be honest.
  • Every tool invocation must go through requestPermission (src/permissions/manager.ts). No direct filesystem or shell calls.
  • Paths resolved to realpath and confined via src/sandbox/fs.ts.
  • Shell commands go through classifyCommandRisk (src/sandbox/shell.ts). critical is hard-blocked — do not add bypasses.
  • Prefer { ok, data } / { ok: false, error } returns. Throw only for programmer errors, using ForgeRuntimeError.
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. yesterday First seen · 22 lines · 0 tokens per session scan A 615d18992780

Subscribe to this mod's changes

tools is a cursor rule published in the GitHub repository hoangsonww/Forge-Agentic-Coding-CLI (22 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 197 tokens. 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.