Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add rjmurillo/ai-agents/plugin install project-toolkitWrote 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/rjmurillo/ai-agents/slashcommandcreator)<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/slashcommandcreator"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/slashcommandcreator/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/rjmurillo/ai-agents/slashcommandcreator"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/slashcommandcreator.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.00051 | $0.02560 |
| Opus 5.5 | $0.00020 | $0.01024 |
| Sonnet 5.5 | $0.00010 | $0.00512 |
| Haiku 4.5 | $0.00005 | $0.00256 |
Grade A, and why
slashcommandcreator 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 22d 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.
How it starts
The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SlashCommandCreator Skill
Purpose
Create production-ready custom slash commands following ai-agents quality standards.
Triggers
create slash command for {purpose}SlashCommandCreator: {description}design slash command that {does something}
When to Use
- User requests "create slash command for [purpose]"
- Repetitive prompts identified in workflow
- Converting manual workflows to automation
- Need reusable, documented command patterns
5-Phase Workflow
Phase 1: Discovery & Analysis
Agent Mode: Analyst
Tasks:
- Clarify user intent: What prompt is being repeated?
- Search existing commands:
ls .claude/commands/**/*.md - Decision: Slash command vs skill (see decision matrix in CLAUDE.md)
- Apply 11 thinking models from skillcreator framework
- Document findings in
.project-toolkit/analysis/slashcommand-[name]-analysis.md
Deliverable: Analysis document with recommendation
Phase 2: Design
Agent Mode: Architect
Tasks:
- Command naming (namespace conventions)
- Argument design:
- Simple commands: use
$ARGUMENTS - Complex commands: use
$1,$2,$3(positional)
- Simple commands: use
- Frontmatter schema:
description(trigger-based per creator-001)argument-hint(if using arguments)allowed-tools(if using bash commands with!or file references with@)model(opus for complex reasoning)disable-model-invocation(if pure prompt template)
- Dynamic context evaluation:
- Bash execution (
!git log --oneline -5) - File references (
@AGENTS.md)
- Bash execution (
- Extended thinking evaluation:
- Add
ultrathinkkeyword for complex reasoning (>5 steps) - Token budget consideration (<31,999 tokens)
- Add
Deliverable: Design specification with frontmatter + prompt
Phase 3: Multi-Agent Validation
Agent Mode: Orchestrator (coordinates 4 agents)
Agents:
- Security:
- Review
allowed-toolsconstraints - Flag overly permissive wildcards
- Verify bash commands are safe
- Review
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 22d ago Changed · +6 lines 3515fc70071f
- 24d ago Changed 1d6cba098675
- 1mo ago Changed 2c33a12b7135
- 1mo ago Changed 4f86d249fd67
- 1mo ago First seen · 275 lines · 51 tokens per session scan A c61c0f4ce924
slashcommandcreator is a skill published in the GitHub repository rjmurillo/ai-agents (48 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 2,560 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
azure-devops-automation
CI/CD pipelines, infrastructure as code, and deployment automation for Azure workloads.
azure-deployment-operations
Production deployment patterns for Azure Static Web Apps, Container Apps, App Service, and infrastructure.
repository-readiness-eval
Evaluate a repository's readiness for AI-assisted development across 4 axes: code understanding, dependency restore, build success, and test execution. Use when onboarding to a new repo, assessing CI readiness, or validating that an AI agent can work effectively in a codebase.
azure-swa-gotchas
Time saved: 2-4 hours per issue.
github-actions-version-upgrades
Older action versions trigger deprecation warnings and will eventually break.
ci-triage
How to find out why a GitHub Actions run failed, and how to tell a real failure from a flake or an infrastructure problem. Use when a check is red, a workflow is stuck, or a run needs re-running.