cashclaw-guard

Enforce runtime limits on LLM calls and tool invocations for unattended agents.

Updated May 26, 2026
One-click install
npx skills add https://github.com/ShageeshanT/cash-claw --skill cashclaw-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cashclaw-guard
Source: https://github.com/ShageeshanT/cash-claw/tree/main/skills/cashclaw-guard
Command: npx skills add https://github.com/ShageeshanT/cash-claw --skill cashclaw-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

CashClaw Guard stops unattended AI agents from blowing through budgets via runaway loops and getting stuck in infinite recursion that keeps calling the LLM or tools.

Core Features & Use Cases

  • Hard cost caps with real-time enforcement: Enforces per-call and per-day USD limits (fails fast instead of waiting for soft limits).
  • Recursive call detection with kill switch: Detects repeating prompt/tool fingerprints within a time window and terminates when thresholds are hit.
  • Tool firewall and rate limiting: Denies unauthorized tools (e.g., shell/exec/eval) and applies per-tool rate caps to reduce blast radius.
  • Operational alerts: Dispatches notifications (Telegram/Slack/Discord per configuration) when budget, recursion, or tool-denial events occur.
  • Use case: Run a production cron agent that periodically checks work and must never exceed a strict spend cap; if recursion starts, Guard kills the loop and alerts you before large charges accumulate.

Quick Start

Ask your agent to run CashClaw Guard initialization and test it once so the policy is written, then verify the guard behavior with a dry-run scenario set.

Frequently Asked Questions about cashclaw-guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent AI agent cost runaway in unattended cron jobs?

Preventing AI agent cost runaway in unattended cron jobs requires real-time budget enforcement via YAML policies that cap per-call and per-day USD limits. The guard fails fast on budget breaches, throwing a BudgetExceeded exception before large charges accumulate.

What is the best way to stop infinite recursion loops in multi-agent workflows?

The best way to stop infinite recursion loops in multi-agent workflows is runtime recursion detection that identifies repeating prompt and tool fingerprints within a specific time window. It terminates the loop immediately with a RecursionKilled exception once thresholds are met.

How do I configure a tool firewall to deny shell and exec access for AI agents?

Configuring a tool firewall to deny shell and exec access for AI agents involves loading a YAML policy that explicitly denies unauthorized tools and applies per-tool rate caps. This reduces the operational blast radius of compromised or looping agent workloads.

Can I send Slack or Telegram alerts when an agent exceeds its budget?

Yes, you can send Slack, Telegram, or Discord alerts when an agent exceeds its budget. The runtime guard dispatches notifications to configured webhook endpoints upon budget, recursion, or tool-denial events, ensuring operational visibility for unattended workflows.

Does this runtime guardrail work with scheduled agent workloads and HYRVE-linked order delivery?

Yes, these runtime guardrails work with scheduled agent workloads and HYRVE-linked order delivery. The enforcement applies to any unattended agent process, containing failures by throwing defined exceptions like BudgetExceeded and RecursionKilled during execution.

Why does my AI agent keep blowing through soft spend limits before failing?

Your AI agent blows through soft spend limits because standard enforcement waits instead of failing fast. Hard cost caps with real-time enforcement stop LLM calls immediately when USD limits are reached, preventing runaway loops from accumulating large charges.