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.
npx agentmods add instructions/effulgent-point/paw/claude-mdgit clone --depth 1 https://github.com/Effulgent-Point/pawWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/effulgent-point/paw/claude-md)<a href="https://agentmods.dev/instructions/effulgent-point/paw/claude-md"><img src="https://agentmods.dev/badge/instructions/effulgent-point/paw/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00812 | $0.00812 |
| Opus 5 | $0.00406 | $0.00406 |
| Sonnet 5 | $0.00162 | $0.00162 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade B, and why
paw CLAUDE.md scanned grade B with 1 finding 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 5d ago.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **`hooks/install_hooks.py`** assumes the `~/.claude/settings.json` layout — specifically a top-level `hooks` object keyed by event name. It edits that file in place. How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
paw — Personal Agent Workforce
What paw is
A lightweight, composable toolkit that gives your AI coding agent standards enforcement, specialized reviewers, and domain knowledge. Every piece works standalone.
How to work in this repo
Composability is the design
Every directory runs independently. Agents work without skills. Hooks work without agents. Rules are plain markdown anyone can read. Don't add cross-directory dependencies.
Agents have scoped permissions
Most agents are read-only. Only 4 of 18 agents have full access (builder, merge-resolver, migration-architect, incident-commander). This is intentional — trust through bounded autonomy.
Rules are the source of truth
If a rule in rules/ contradicts how an agent behaves, fix the agent. Rules don't bend to implementation convenience.
Tests before code
The builder agent writes failing tests first, then implementation. The test-runner agent verifies. The auto_test_detect hook warns on missing tests.
Git rules
- Always
git pull(merge, not rebase) before push - Never
git rebaseagainst published history - Never
git push --forceto any branch - Never commit to
maindirectly — use a feature branch - Always verify
git branchshows the intended branch before committing
These are enforced by hooks/git_safety.py and hooks/branch_guard.py.
Adding an agent
- Pick the context it loads from
contexts/. - Pick the rules it references from
rules/. - Define minimum tools — least privilege.
- Write the role, process, outputs, done-when.
- Add to
agents/README.md.
Load contexts/X in an agent file is a prompt directive, not a mechanical import. The AI tool reads the line and opens the file itself. This works in Claude Code, where agent files are loaded into context and the agent can read the repo. In other tools, you may need to paste or otherwise include the referenced context and rule files manually.
Adding a rule
- Write the statement, why, hard rules, soft rules.
- Identify which agents/hooks enforce it.
- Update relevant agents to reference the new rule.
- Add to
rules/README.md.
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.
- 5d ago First seen · 67 lines · 812 tokens per session scan B 2c5359894cfe
paw CLAUDE.md is an instructions file published in the GitHub repository Effulgent-Point/paw (2 stars, last pushed 25d ago), licensed MIT. It adds 812 tokens to every session, about $0.0041 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
langgraph AGENTS.md
AGENTS.md instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
hatch3r CLAUDE.md
Claude Code instructions for hatch3r/hatch3r, covering hatch3r — development instructions, architecture, development commands, two-axis pillar framework (2.0.0) and orchestrator self-discipline (bypass protection).
aeon CLAUDE.md
Claude Code instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
ken CLAUDE.md
Claude Code instructions for townsendmerino/ken, covering claude.md, what this is, repository ownership (read this first), commands and embedding parity & golden fixtures (now in aikit).
cortex AGENTS.md
AGENTS.md instructions for tools-for-agents/cortex, covering agents.md — cortex, setup, the rules this repo is built on, tests and ci.
CustomerNewsletter copilot-instructions.md
Instructions for briancl2/CustomerNewsletter, covering copilot instructions, mission, always read first, core workflow and rules.