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/n9e/fe/simplifygit clone --depth 1 https://github.com/n9e/feWhat 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.00048 | $0.01078 |
| Opus 5 | $0.00024 | $0.00539 |
| Sonnet 5 | $0.00010 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
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 today.
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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/simplify — Code Simplification
When the user invokes /simplify [scope], review code for safe simplifications and apply them with user approval.
| Command | Scope | What gets reviewed |
|---|---|---|
/simplify |
uncommitted | Staged + unstaged changes (default) |
/simplify HEAD~N |
recent commits | Changes in the last N commits |
/simplify <file> |
single file | Only that file |
Workflow
1. Determine Scope
Default to uncommitted changes when no argument is provided.
git status --short --branch
For uncommitted changes:
git diff --staged --name-only
git diff --name-only
For commit range (e.g., HEAD~3):
git diff HEAD~3 --name-only
For a single file, verify it exists and read it.
Stop if:
- no changed files in the requested scope
- merge conflicts are present
2. Read And Analyze
Read the full content of each changed file (not just the diff) so that simplifications are informed by surrounding context.
Look for:
| Category | Examples |
|---|---|
| Dead code | Unused imports, unreachable branches, commented-out blocks, unused variables/functions |
| Redundant logic | Duplicate conditions, double negation, unnecessary else after return, if x return true else return false |
| Naming | Misleading names, single-letter variables in non-trivial scope, inconsistent conventions within the file |
| Type tightening | Overly broad types (any, interface{}), missing return types, unnecessary type assertions |
| Unnecessary wrappers | Trivial wrapper functions, redundant intermediate variables, over-abstracted single-use helpers |
| Simplifiable expressions | Ternaries that can be boolean expressions, verbose null checks replaceable by optional chaining, long-form iterations replaceable by standard library calls |
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.
- today First seen · 153 lines · 48 tokens per session scan A 87e6b5f4cf84
simplify is a command published in the GitHub repository n9e/fe (302 stars, last pushed today), licensed Apache-2.0. It adds 48 tokens to every session and 1,078 once invoked, about $0.0002 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-09-01.
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.