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/vignesh2027/ai-agent-skills/simplifygit clone --depth 1 https://github.com/vignesh2027/AI-AGENT-SKILLSWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/vignesh2027/ai-agent-skills/simplify)<a href="https://agentmods.dev/commands/vignesh2027/ai-agent-skills/simplify"><img src="https://agentmods.dev/badge/commands/vignesh2027/ai-agent-skills/simplify.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00000 | $0.00139 |
| Opus 5 | $0.00000 | $0.00069 |
| Sonnet 5 | $0.00000 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
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 5d 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
Load skills/code-simplification/SKILL.md.
Simplify the code described. Apply Chesterton's Fence: understand why each piece exists before removing it.
Simplification targets:
- Dead code (never executed)
- Premature abstraction (more complex than what it abstracts)
- Unnecessary indirection
- Redundant comments (that say what the code already says)
- Magic numbers and strings
- Over-engineered error handling
- Duplicate logic
Rules:
- Understand before removing
- One simplification at a time
- Run tests after each change
- No behavior changes (tests must pass)
- Validate: is it actually simpler for a new reader?
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.
- 5d ago First seen · 20 lines · 0 tokens per session scan A 375acb44c17a
simplify is a command published in the GitHub repository vignesh2027/AI-AGENT-SKILLS (2 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 139 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-31.
Other commands, from other repositories
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
speckit.opsmill.retrospect
Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
create-issue
Transform feature descriptions, bug reports, or improvement ideas into well-structured GitHub issues.
release-plan
Command "release-plan" from alisunstar/OpenSunstar, covering /rd:release-plan — 发布计划, 先读, 执行, 产物 and 人工确认.
mach12:gh-pr-read
Read a GitHub pull request's title, body, and all top-level PR conversation comments; optionally locate an HTML-marker comment.