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-argsnpx skills add fayis672/slash-IT --skill create-cmd-argsgit 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-args)<a href="https://agentmods.dev/skills/fayis672/slash-it/create-cmd-args"><img src="https://agentmods.dev/badge/skills/fayis672/slash-it/create-cmd-args.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.00548 |
| Opus 5 | $0.00009 | $0.00274 |
| Sonnet 5 | $0.00004 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
create-cmd-args 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 3d 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 — and save it as a reusable custom slash command that is parameterized, so the variable parts become arguments.
Raw arguments: $ARGUMENTS
Do this:
- Parse
$ARGUMENTSinto a name and an optional scope flag:--global/-g/global-> system-wide.--project/-p/project-> 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 with AskUserQuestion: "Where should
/<name>be saved?" -> Global or Project. - Global path:
~/.claude/commands/ - Project path:
<current working directory>/.claude/commands/— create if missing; fall back to Global if not in a project 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).
- Identify the parts of the prompt that are specific values likely to change each run — a
filename, a topic, a function/variable name, a language, a count, etc. Replace them with
placeholders:
- One variable ->
$ARGUMENTS. - Multiple variables ->
$1,$2,$3in the order they should be passed. Keep the fixed instructions intact.
- One variable ->
- Add YAML frontmatter with a one-line
descriptionand anargument-hintlisting the placeholders in order, e.g.argument-hint: <filename> <language>. - Show the user the parameterized prompt and how to call it (e.g.
/<name> utils.js python). - 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.
- 3d ago First seen · 41 lines · 18 tokens per session scan A 3e1c67be010c
create-cmd-args 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 548 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
workflow
Professional AI programming assistant with structured workflow (Research -> Ideate -> Plan -> Execute -> Optimize -> Review) for developers.
r3f-animation
React Three Fiber animation - useFrame, useAnimations, spring physics, keyframes. Use when animating objects, playing GLTF animations, creating procedural motion, or implementing physics-based movement.
golden-rss
Use when testing the rss golden build.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.