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 skills add fayis672/slash-IT --skill list-cmdsgit 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/list-cmds)<a href="https://agentmods.dev/skills/fayis672/slash-it/list-cmds"><img src="https://agentmods.dev/badge/skills/fayis672/slash-it/list-cmds/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/fayis672/slash-it/list-cmds"><img src="https://agentmods.dev/badge/skills/fayis672/slash-it/list-cmds.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.00210 |
| Opus 5.5 | $0.00012 | $0.00084 |
| Sonnet 5.5 | $0.00006 | $0.00042 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
list-cmds 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 1mo 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
List the user's custom slash commands so they can see what they've saved.
Do this:
- Read the user's global commands directory
~/.claude/commands/and find every*.mdfile (ignoreREADME.md). - Also check the current project's
.claude/commands/directory if it exists. - For each command file, show:
- the command name (filename without
.md, prefixed with/), - its
descriptionfrom the frontmatter (or the first line if no frontmatter), - whether it is global (user) or project.
- the command name (filename without
- Present them as a simple, readable list grouped by global vs project.
- If there are none, say so and remind the user they can create one with
/slash-it:create-cmd <name>.
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.
- 1mo ago First seen · 18 lines · 30 tokens per session scan A 3a3eb8170a60
list-cmds is a skill published in the GitHub repository fayis672/slash-IT (2 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 210 once invoked, about $0.0001 per session on Opus 5.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
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
whats-next
Suggest what to work on next based on recent activity and current context. Use when the user is between tasks, at a decision point, wants direction on where to focus, or asks what to do next.
coaching-mode
Use when the user wants to coach someone — a report, peer, or mentee — through a problem rather than solve it for them. Trigger phrases include "coach me through how to talk to [report]", "I want to help [name] figure out X without telling them what to do", "let me practice a coaching conversation", "GROW conversation…
manage-glue-workers
Use when managing engineers who naturally gravitate toward glue work (onboarding, documentation, unblocking, process improvement) and need protection from burnout, visibility for their impact, and career development that doesn't force them off the IC track. Trigger phrases include "my report does too much glue", "how…
user-profile
Use to create or update the user's anchor profile — a single private file (/bettersense-work-reflections/profile.md) that captures who the user is, what they do, what context other skills need to know about them. Read automatically by other skills in the bundle when present, so the user doesn't re-explain themselves…
workload-equity
Use when the user wants to analyze whether non-promotable (glue) work is fairly distributed across their team, with attention to demographic and seniority patterns. Trigger phrases include "is our glue work fair", "who does the non-promotable work on our team", "audit workload distribution", "are women doing more glue…