obey
Description
You tell Claude "never push to main." Claude agrees. Five minutes later, Claude pushes to main.
Installation
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open the source below and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
README
obey
Makes Claude actually follow your rules.
The problem
You tell Claude "never push to main." Claude agrees. Five minutes later, Claude pushes to main.
The memory system is passive — Claude writes rules down but doesn't actively check them. Hooks exist but require manual regex setup. There's no way to say "remember this" and have it actually stick.
The solution
**obey** is a Claude Code plugin that stores your rules, injects them into every session, and actively blocks violations.
/remember never push to main
# → Rule saved (global, hook-enforced)
# → Claude is now blocked from running "git push origin main"
/remember always explain your reasoning before writing code
# → Rule saved (global, instruction)
# → Injected at the start of every session as a reminder
/remember never use .unwrap() --rust
# → Rule saved (Rust projects only, blocks .unwrap() in code)
That's it. Rules persist across sessions, survive context compaction, and get actively enforced.
How it works
You say: "/remember never force push"
│
obey evaluates the rule:
├── Scope: global (applies everywhere)
├── Mechanism: hook (can be blocked by code)
├── Pattern: git push --force
└── Saved to ~/.config/obey/global-rules.json
│
Next session starts:
├── SessionStart hook fires
├── All rules injected into Claude's context
└── Claude sees: "RULE: Never force push"
│
Claude tries: git push --force
├── PreToolUse hook fires
├── Pattern matches → BLOCKED
├── Claude sees: "Rule violated: Never force push"
└── Claude adjusts behavior
Install
From marketplace
/plugin marketplace add https://github.com/Lexxes-Projects/lexxes-plugins.git
/plugin install obey@lexxes-plugins
Local development
claude --plugin-dir /path/to/obey
...
Related Skills
Defense in Depth
Implement multi-layered testing and security best practices.
Security SecLists Official Repository
[OWASP Testing Guide](https://owasp.org/www-project-web-security-testing-guide/)
Security Threat Hunting with Sigma Rules
Use Sigma detection rules to hunt for threats and analyze security events
Security Maintenance Walkthrough - 2026-03-29
- Re-triaged the full 2026-03-15 security finding set against current `main` and wrote a fresh current-head re
Security Google Workspace Model Armor
Filter user-generated content for safety
Security Google Workspace Alert Center
Manage security alerts
Security Related Agents
Token Auditor
Scans ui/src/ for hardcoded visual values, duplicate components, and shadcn replacement candidates; produces d
Gitnexus Security Boundary Reviewer
GitNexus security and trust-boundary reviewer. Use for auth, permissions, secrets, injection, unsafe parsing,
Accessibility Audit
| You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive tec... | -