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/neurofoo/agent-skills/simplifygit clone --depth 1 https://github.com/neurofoo/agent-skillsWhat 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.00000 | $0.00316 |
| Opus 5 | $0.00000 | $0.00158 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00032 |
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.
What it actually says
Simplify Explanation
Take an explanation and make it simpler and clearer.
Instructions
Analyze the provided explanation and rewrite it in simpler terms. Remove jargon, shorten sentences, add analogies.
Output Format
Original: [The explanation to simplify]
Analysis
Complexity Issues Found
| Issue | Example from Original |
|---|---|
| Jargon | "[term] - not defined" |
| Long sentences | "[quote first few words...]" |
| Abstract concepts | "[what's not concrete]" |
| Assumed knowledge | "[what reader needs to already know]" |
Reading Level: [Approximate grade level of original]
Simplified Version
[Rewritten explanation with:
- Jargon replaced with plain words
- Sentences shortened
- Concrete examples added
- Analogies included]
What Changed
| Original | Simplified | Why |
|---|---|---|
| "[phrase]" | "[simpler phrase]" | [reasoning] |
| "[phrase]" | "[simpler phrase]" | [reasoning] |
Added Analogy
[A new analogy to help understanding]
The 30-Second Version
If someone only has 30 seconds:
[Ultra-condensed explanation]
Guidelines
- Simpler ≠ dumbed down; simpler = clearer
- Every jargon term should be either removed or defined
- Add examples for abstract concepts
- Test: Would this make sense to someone outside the field?
$ARGUMENTS
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 · 69 lines · 0 tokens per session scan A a638495b1923
simplify is a command published in the GitHub repository neurofoo/agent-skills (111 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 316 tokens. 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.