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 commands/patrickclery/ruly/decomposegit 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.00021 | $0.02059 |
| Opus 5 | $0.00010 | $0.01030 |
| Sonnet 5 | $0.00004 | $0.00412 |
| Haiku 4.5 | $0.00002 | $0.00206 |
Grade A, and why
ruly:decompose 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 yesterday.
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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ruly:decompose Command
Overview
The /ruly:decompose command splits a markdown file into a directory of separate files based on its section headers. It uses git mv to preserve history, moving the original file to become the index file (_common-{tag}.md) that references all extracted sections via anchor links.
Usage
/ruly:decompose <file> <directory>
Arguments
<file>- The markdown file to decompose<directory>- The name for the output directory (e.g., "standards", "patterns")
Examples
# Decompose common.md into a "standards" directory
/ruly:decompose rules/workaxle/core/frameworks/common.md standards
# Decompose debugging.md into a "troubleshooting" directory
/ruly:decompose rules/bug/debugging.md troubleshooting
Example Transformation
Before (rules/core/common.md):
---
description: Common Ruby patterns
globs:
- '**/*.rb'
---
# Ruby Language Patterns
## Code Style
Content about code style...
## Error Handling
Content about error handling...
## Testing
Content about testing...
After decomposition into standards/:
rules/core/standards/
├── _common-ruby-language-patterns.md # Index (original file, moved via git mv)
├── code-style.md # Extracted section
├── error-handling.md # Extracted section
└── testing.md # Extracted section
standards/_common-ruby-language-patterns.md (index):
---
description: Common Ruby patterns
globs:
- '**/*.rb'
requires:
- ./code-style.md
- ./error-handling.md
- ./testing.md
---
# Ruby Language Patterns
## Code Style
See [Code Style](#code-style) for code style patterns.
## Error Handling
See [Error Handling](#error-handling) for error handling patterns.
## Testing
See [Testing](#testing) for testing patterns.
standards/code-style.md:
---
description: Code style guidelines
alwaysApply: false
---
# Code Style
Content about code style...
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.
- yesterday First seen · 302 lines · 21 tokens per session scan A 37e8860e8d6f
ruly:decompose is a command published in the GitHub repository patrickclery/ruly (5 stars, last pushed 6d ago), licensed MIT. It adds 21 tokens to every session and 2,059 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.