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 skills/fayis672/slash-it/create-cmd-optimisenpx skills add fayis672/slash-IT --skill create-cmd-optimisegit clone --depth 1 https://github.com/fayis672/slash-ITWrote 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/skills/fayis672/slash-it/create-cmd-optimise)<a href="https://agentmods.dev/skills/fayis672/slash-it/create-cmd-optimise"><img src="https://agentmods.dev/badge/skills/fayis672/slash-it/create-cmd-optimise.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 | $0.00018 | $0.00569 |
| Opus 5 | $0.00009 | $0.00284 |
| Sonnet 5 | $0.00004 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
create-cmd-optimise 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 4d 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
The user wants to take their previous message — the most recent user turn in this conversation before this invocation — improve it into a stronger prompt, and save the improved version as a reusable custom slash command.
Raw arguments: $ARGUMENTS
Do this:
- Parse
$ARGUMENTSinto a name and an optional scope flag:--global/-g/global-> save system-wide.--project/-p/project-> save to the current project.- Everything else is the command name.
- If no name is given, STOP and ask for one. A name is required.
- Determine where to save (scope):
- If a scope flag was given, use it.
- Otherwise, ASK the user with AskUserQuestion: "Where should
/<name>be saved?" with options Global (all projects) and Project (this repo only). - Global path:
~/.claude/commands/ - Project path:
<current working directory>/.claude/commands/— create it if missing. If not in a project, fall back to Global and say so.
- Normalize the name: lowercase, kebab-case, strip any leading
/and.md. - Find the user's previous prompt (the message right before this call).
- Rewrite it into a clear, well-structured, high-quality prompt while preserving the original
intent. Apply prompt-engineering best practices:
- Make the goal explicit and unambiguous.
- Add useful structure (numbered steps, expected output format) where it helps.
- Fix grammar/spelling and tighten vague wording.
- Where the prompt clearly takes input, parameterize it with
$ARGUMENTS(or$1,$2). - Do NOT add scope the user never asked for.
- Briefly show the user a before/after diff of the prompt (1-3 lines is fine).
- Add YAML frontmatter with a one-line
descriptionand, if you added parameters, anargument-hint. - Write the file to
<chosen path>/<name>.md. - If that file already exists, show its current contents and ask before overwriting.
- Confirm: print the saved file path, the scope, and that
/<name>is now available.
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.
- 4d ago First seen · 42 lines · 18 tokens per session scan A 66453667bfec
create-cmd-optimise is a skill published in the GitHub repository fayis672/slash-IT (2 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 569 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 skills, from other repositories
remove-ai-marks
Strip multi-vendor AI provenance from owned files: hidden Unicode (Layer A), statistical sampling watermarks via rewrite (Layer B — always offer), and C2PA/EXIF/XMP/container metadata on PNG/JPEG/WebP/SVG/PDF/DOCX/ODT/HTML/MD. Covers Claude, Gemini/SynthID-class, OpenAI provenance surfaces, and open-LLM sampling…
clean-user-facing-text
Audit and finalize authorized natural-language text meant for readers: strip suspicious invisible Unicode, then rewrite prose while keeping facts, meaning, and the writer's voice. Use when the user asks to clean, humanize, polish, or finalize articles, manuscripts, reports, documentation, emails, product copy, UI…
repo-visuals
Create hero visuals — animated GIF, static PNG, or animated SVG — for GitHub repositories. Runs a structured discovery conversation (scan repo → recommend format → propose creative scenarios → agree on a brief), then designs bespoke HTML/SVG, previews it in the browser, and exports. Use when the user asks for a README…
generate-tests
Generate unit tests for a .NET service following the coverage-kit conventions. Use when the user asks to 'generate tests', 'backfill tests', 'characterize this service', or 'add tests for' a target after coverage-init has run. Operates in characterization mode (freeze current behavior for existing code) or spec mode…
repo-visuals-retro
Retrospective meta-skill for the repo-visuals skill. Reads accumulated evaluation logs from past runs, spots patterns (recurring low-score criteria, repeated iteration failures, unsatisfied requests), consults other expert skills (skill-creator, frontend-design, etc.) where relevant, and proposes concrete edits to…
hyper-plan-loop
Use when a plan should be produced and critic-hardened in one gesture — plan → Codex review → revise, repeated until clean. Also when the user invokes /hyperclaude:hyper-plan-loop. For manual round-by-round control use /hyperclaude:hyper-plan + /hyperclaude:hyper-plan-review instead.