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/patrickclery/ruly/claude-mdgit clone --depth 1 https://github.com/patrickclery/rulyWhat 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.01093 | $0.01093 |
| Opus 5 | $0.00547 | $0.00547 |
| Sonnet 5 | $0.00219 | $0.00219 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
ruly CLAUDE.md scanned grade A with 0 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 2d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
- always update the ~/.config/ruly/recipes.yml and /Users/patrick/Projects/chezmoi/config/ruly/recipes.yml when you change things it references (they should be identical)
- Every time the slash commands are updated, make sure to update the slash command section of README.md
- When changing
rulyCLI commands (squash, clean, analyze, mcp, etc.), always update README.md to reflect the changes - NEVER edit
CLAUDE.local.md— it is generated output fromruly squashand will be overwritten. Fix the source rules in ./rules/ instead. - When I ask to change rules, don't change the rules in .claude/ always look in ./rules/
- When I ask to create a skill, add it to
rules/{tag}/skills/{skill-name}.md(Ruly searches for skills in that structure) - Skills in rules/ are regular
.mdfiles, NOTSKILL.md- Ruly converts them to SKILL.md format on squash - Always use
git mvto move/rename files instead of deleting and re-creating them (preserves git history) - When deleting/moving/renaming files in rules/, always search for references to update:
requires:frontmatter in other rule files- Recipe files (recipes.yml, ~/.config/ruly/recipes.yml)
- Section anchor links that may have changed
- When I say "commit" or "commit all", commit and push ALL modified files in BOTH repos (don't assume any changes are unrelated):
- The rules submodule (./rules) → https://github.com/patrickclery/rules
- The parent ruly repo → https://github.com/patrickclery/ruly (update submodule reference)
- Always use Mermaid for diagrams/flowcharts in rules (never graphviz/dot). Exception: Jira/Confluence don't support Mermaid, so use ASCII diagrams there instead.
Claude Code Instructions
Ruly Recipe and MCP Configuration Patterns
Import Ruly recipe configuration patterns and MCP server guidelines. @./.claude/ruly-recipes-mcp-patterns.md
- When testing out
ruly squash ..., always run it from amktmpdirand not the main project directory - always update ruly after any changes. for instance, /Users/patrick/.local/share/mise/installs/ruby/3.3.3/bin/ruly is out of sync right now
- Whenever you want token counts for recipes, run
ruly statsand read the results fromstats.md - After any changes to the
corerecipe (eitherrecipes.ymlor any file it references), run:cd ~/agents/core && ruly squash --deepclean core. Do this before ending the session — check whether any file you modified is referenced by the core recipe.
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.
- 2d ago First seen · 93 lines · 1,093 tokens per session scan A 57d2ac489e48
ruly CLAUDE.md is an instructions file published in the GitHub repository patrickclery/ruly (5 stars, last pushed 7d ago), licensed MIT. It adds 1,093 tokens to every session, about $0.0055 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.