AgentSentinel Safety Layer
Local-first budget and policy guardrails for agent actions, with optional remote sync to AgentSentinel.
jimmystacks
@jimmystacks
What This Skill Does
Local-first policy and budget guardrails that gate agent actions before execution. Checks proposed commands against a local policy file and budget, blocking or allowing them accordingly.
Replaces manual oversight of agent spending and destructive actions by enforcing local policy and budget caps automatically.
When to Use It
- Check if a costly model API call is allowed under current budget
- Block a destructive shell command like file deletion before it runs
- Prevent high-volume automation loops from exceeding a spend limit
- View current local budget usage and policy status
- Reset local spend tracking after a completed run or session
- Upload locally recorded action events to the AgentSentinel cloud for centralized monitoring
Install
$ openclaw skills install @jimmystacks/agent-sentinelAgentSentinel Protection Layer
Use this skill when you want a local policy gate before an agent performs a costly or risky action.
This OpenClaw skill is the lightweight entry point to the broader AgentSentinel product:
- this skill for local-first OpenClaw guardrails
- AgentSentinel SDK for deeper Python agent instrumentation
- AgentSentinel platform for centralized monitoring, dashboards, and approval workflows
AgentSentinel is local-first by default:
- Policy checks run locally.
- Budget tracking runs locally.
- No remote sync is attempted unless the operator runs
syncwith an API key configured.
When To Use It
Use AgentSentinel before:
- expensive model or API calls
- file deletion or destructive shell commands
- high-volume automation loops
- actions that should be blocked by policy or capped by budget
Commands
check
Check whether a proposed action is allowed under the current local policy and budget.
python3 sentinel_wrapper.py check --cmd "rm -rf build" --cost 0.05
status
Show the current local status, including budget usage and whether optional remote sync is enabled.
python3 sentinel_wrapper.py status
sync
Upload locally recorded events to AgentSentinel cloud when AGENT_SENTINEL_API_KEY is set.
python3 sentinel_wrapper.py sync
bootstrap
Create a default callguard.yaml in the current workspace if one does not already exist.
python3 sentinel_wrapper.py --bootstrap
reset
Reset local tracked spend for the current run, or for the entire local session state.
python3 sentinel_wrapper.py reset --scope run
python3 sentinel_wrapper.py reset --scope all
Configuration
Policy is loaded from callguard.yaml in the current workspace when present.
Optional cloud mode is enabled by setting:
AGENT_SENTINEL_API_KEY
If the API key is not present, the skill remains local-only.
Locally recorded events stay on-machine until sync is run.
AgentSentinel Product Path
Use this skill if you want fast local guardrails inside OpenClaw.
Use the AgentSentinel SDK when you want:
- richer Python integrations
- broader policy and telemetry coverage
- framework-level instrumentation outside OpenClaw
Use the AgentSentinel platform when you want:
- centralized visibility across agents
- dashboards and historical analysis
- human approval workflows and operational review
External Endpoints
| Endpoint | When it is called | Data sent |
|---|---|---|
https://api.agentsentinel.dev | Only when AGENT_SENTINEL_API_KEY is present and python3 sentinel_wrapper.py sync is run | locally recorded action events generated by AgentSentinel |
Security And Privacy
- Local mode does not send data off-machine.
- The wrapper does not write API keys to
.envor other files. - Remote sync is opt-in and requires both
AGENT_SENTINEL_API_KEYand an explicitsynccommand. - If remote sync fails, policy checks still continue locally.
Model Invocation Note
OpenClaw may invoke this skill automatically when the task suggests budget enforcement, policy checks, or action gating. That behavior is expected for an installed skill.
Trust Statement
By enabling remote sync, you allow AgentSentinel telemetry to be sent to agentsentinel.dev. Only enable that mode if you trust the service and want centralized monitoring.
Top skills in this category
self-improving agent
@pskoettCaptures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude rea
Skill Vetter
@spclaudehomeSecurity-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
Self-Improving + Proactive Agent
@ivangdavilaSelf-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
Proactive Agent
@halthelobsterTransform AI agents from task-followers into proactive partners that anticipate needs and continuously improve. Now with WAL Protocol, Working Buffer, Autonomous Crons, and battle-tested patterns. Part of the Hal Stack ๐ฆ
Agent Browser
@matrixyHeadless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection