djayamah

Usewarden — AI skill for Claude Code

AI community

Free, local guardrail for AI coding agents — Claude Code, Cursor, Gemini CLI and more.

How to install Usewarden

This entry records only its repository, not the path inside it, so there is no exact command to give. Open djayamah/usewarden and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Usewarden does

Free, local guardrail for AI coding agents — Claude Code, Cursor, Gemini CLI and more. Blocks out-of-scope writes, .env reads, rm -rf and force pushes. No API key, no account, no telemetry by default.

Alternatives in AI

  • Define — Definition phase - Clarify and scope problems with multi-AI consensus 2.8k ★
  • Todos — Strategic roadmap for agent-skill-manager — the npm for AI skills 185 ★
  • Datafog Python — Offline PII firewall for AI agents and LLM apps: fast local detection and redaction, Claude Code hook, LiteLLM 69 ★

README

usewarden

**Stop your AI coding agent before it touches something it shouldn't.**

One local guardrail for Claude Code, Cursor, Gemini CLI, Copilot CLI, Codex and OpenCode. It blocks writes outside the repo you're in, `.env` reads, `rm -rf` above the project root, force pushes to `main`, and `curl | sh` — deterministically, in under a millisecond, with **no API key and no tokens**.

Free. Local. No account.

Two people opened issues asking this before anything else, so it belongs here rather than in a FAQ ([#9](https://github.com/djayamah/usewarden/issues/9), [#14](https://github.com/djayamah/usewarden/issues/14)).

  • It is free. MIT licence. No paid tier, no account, no sign-up, no trial. npm install -g usewarden is the whole transaction.
  • It needs no API key. The blocking is deterministic pattern and scope matching: zero tokens, zero API calls, on every event. The one thing that can ever cost money is the optional Layer 2 drift judge, and only if you hand it your own key for a paid API. Give it nothing and it says so and the blocking carries on.
  • Your code stays on your machine. Layer 1 never leaves it. Telemetry is off by default and this version ships no endpoint at all, so there is nowhere for a payload to go. The single exception is that optional judge, which you switch on yourself, to a provider you pick, with your own key — and its input is redacted and length-capped before it goes.

Longer answers in the [FAQ](#faq).

![Two incident cards from a real agent session: a Layer 1 block of `rm -rf` outside the repo, and the Layer 2 drift judge flagging the same action](assets/incident-card.png)

*Real output from a real `claude --dangerously-skip-permissions` session. The agent read the reason, stopped, and explained itself instead of routing around the block.*

Is this your week?

  • "It deleted files I never asked it to touch." rm -rf ~/ and its cousins are now a recurring, publ