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/strale-io/strale/claude-mdgit clone --depth 1 https://github.com/strale-io/straleWrote 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/strale-io/strale/claude-md)<a href="https://agentmods.dev/instructions/strale-io/strale/claude-md"><img src="https://agentmods.dev/badge/instructions/strale-io/strale/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.13277 | $0.13277 |
| Opus 5 | $0.06638 | $0.06638 |
| Sonnet 5 | $0.02655 | $0.02655 |
| Haiku 4.5 | $0.01328 | $0.01328 |
Grade C, and why
strale CLAUDE.md scanned grade C with 2 findings 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 3d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
**Second failure mode:** creating a Windows directory junction from a temporary worktree to the main checkout's `node_modules`, then later removing that worktree with `rm -rf`, follows the junction and **deletes the real Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
For wire-shape ↔ consumer-shape contracts (where backend uses one set of names and the frontend normalizer maps to different names — e.g. backend `fallback_capability` → frontend `capability_slug`), the shape-check scrip How it starts
The opening of the file, as written. The whole thing — 577 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Protocol
Session Start
- Declare session intent (one sentence: what is this session for?)
- Determine mode:
- Quick: Bug fix, config change, single small component (<2 hours, no design decisions)
- Full: New feature, design exploration, multi-component work, anything requiring decisions
- Escalation triggers: second feature touched, design decision emerges, >2hr estimate, contradiction detected. See .claude/PROTOCOL.md for full criteria and protocol definitions.
Notion Access (REQUIRED)
- Project Home: https://www.notion.so/31167c87-082c-81fb-96da-d3188d34aa72
- To-do & Build Plan: https://www.notion.so/33c67c87-082c-81c3-a72b-cc59b10ff4ac
- Decisions DB: ea57671f-7167-44e4-a254-c0a1de79e7f9
- Governance: How we work > How this workspace works (33c67c87-082c-81ea-8417-c4a701d68611)
Notion Workspace Structure (8 sections under Project Home)
- 🏠 Start Here — overview + navigation
- 🎯 Strategy — what Strale is, the problem, opportunity, competitive landscape, business model
- 🛠️ Products — SQS, Audit Trail, Discovery, Capabilities & solutions, Feature Registry DB
- ✅ To-do & Build Plan — THE ONLY task list (To-do DB + Deferred DB)
- 📣 Go-to-market — distribution surfaces, activation funnel, brand & voice, social media, Social Media Posts DB
- 🔧 Internals — testing system, testing rules, onboarding pipeline, bug fix framework, tech stack
- 📓 Journal — session logs, brainstorms, analyses (Journal DB)
- ⚙️ How we work — working rules, governance, Decisions DB, Glossary DB
Notion Governance Rules (enforced)
- Check before creating — look at the page directory before creating any new page
- ONE page per topic — never create v2, update existing subpage
- Brainstorms go to Journal DB, not as standalone pages
- To-do DB is THE ONLY task list — action items never live in prose
- Superseded pages archived same session (prefix + move to archive)
- Search existing pages before creating new ones
GitHub Access (REQUIRED)
- Repo: strale (local)
- Main branch: main
- Feature branch pattern: type/kebab-description
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.
- 3d ago First seen · 577 lines · 13,277 tokens per session scan C 5b48236cfdce
strale CLAUDE.md is an instructions file published in the GitHub repository strale-io/strale (4 stars, last pushed 4d ago), licensed MIT. It adds 13,277 tokens to every session, about $0.0664 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
quality-oracle CLAUDE.md
Claude Code instructions for assister-xyz/quality-oracle, covering laureum.ai (quality oracle), project context, architecture, running locally and quality gates.
teamretro-mcp-server copilot-instructions.md
Copilot instructions for adepanges/teamretro-mcp-server, covering copilot coding agent instructions, project overview, tech stack, build & run commands and build errors to watch for.
f5xc-api-mcp CLAUDE.md
Claude Code instructions for robinmordasiewicz/f5xc-api-mcp, covering claude code project instructions, repository workflow, making changes (steps 1-5), waiting for auto-merge (step 6) and post-merge monitoring (steps 7-8).
motormetrics AGENTS.md
AGENTS.md instructions for motormetrics/motormetrics, covering codex instructions, beads issue tracker, quick reference, rules and issue tracking with bd (beads).
ESAA-Core AGENTS.md
Instructions for elzobrito/ESAA-Core, covering agents.md — contrato operacional codex/esaa, 1. autoridade e termos, 2. cli e runner, ou configure o runner uma vez por sessão and 3. concorrência.
cutover-mcp-public AGENTS.md
Instructions for gocutover/cutover-mcp-public, covering agents.md, what this is, prerequisites, setup and environment variables.