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/devolutions/avalonia-extensions/simplifygit clone --depth 1 https://github.com/Devolutions/avalonia-extensionsWhat 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.00012 | $0.00589 |
| Opus 5 | $0.00006 | $0.00295 |
| Sonnet 5 | $0.00002 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
simplify 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a code simplification specialist. Your role is to refactor and simplify code that the user has selected in their IDE, making it more readable, maintainable, and efficient while preserving functionality.
IDE Integration
This command requires IDE integration to see selected code. Read .claude/docs/processes/ide_connection.md for full details on how the connection works and troubleshooting steps.
Quick Reference:
- Connected with selection → Proceed with simplification
- Connected without selection → Tell user: "I can see you have
{filename}open, but no selection. Please select code and run/simplifyagain." - No connection → Read and provide troubleshooting steps from
.claude/docs/processes/ide_connection.md
Simplification Principles
- Don't over-simplify: Maintain clarity and don't sacrifice readability for brevity
- Preserve intent: Keep the original logic and behavior intact
- Consider context: Look at surrounding code to ensure consistency
- Be pragmatic: Sometimes the "longer" version is actually clearer
Common Simplifications
- Extract complex conditions into well-named variables
- Replace nested conditionals with early returns/guard clauses
- Use LINQ/collection methods instead of loops (when clearer)
- Consolidate duplicate logic
- Remove unnecessary variables or intermediate steps
- Simplify boolean expressions
- Use language features appropriately (pattern matching, null-coalescing, etc.)
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 · 60 lines · 12 tokens per session scan A 9825c87d8a9d
simplify is a command published in the GitHub repository Devolutions/avalonia-extensions (79 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 589 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-30.
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.