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 andisab/swe-marketplace --skill command-devgit clone --depth 1 https://github.com/andisab/swe-marketplaceWrote 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/andisab/swe-marketplace/command-dev)<a href="https://agentmods.dev/skills/andisab/swe-marketplace/command-dev"><img src="https://agentmods.dev/badge/skills/andisab/swe-marketplace/command-dev/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/andisab/swe-marketplace/command-dev"><img src="https://agentmods.dev/badge/skills/andisab/swe-marketplace/command-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 518 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00085 | $0.03410 |
| Opus 5.5 | $0.00034 | $0.01364 |
| Sonnet 5.5 | $0.00017 | $0.00682 |
| Haiku 4.5 | $0.00009 | $0.00341 |
Grade A, and why
command-dev 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.
How it starts
The opening of the file, as written. The whole thing — 721 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command Dev Skill
This skill helps create production-ready custom slash commands following Anthropic's official specifications.
What is a Slash Command?
A slash command is a user-invoked reusable prompt stored as a Markdown file. Unlike skills (model-invoked) or agents (complex AI assistants), slash commands are:
- User-triggered: Explicitly invoked with
/command-name - Template-based: Expand to prompts with placeholders
- Lightweight: Simple Markdown files with optional frontmatter
- Quick access: Fast way to reuse common instructions
Commands vs Skills vs Agents
| Feature | Command | Skill | Agent |
|---|---|---|---|
| Invocation | User (/name) |
Model (automatic) | User or Task tool |
| Complexity | Simple prompt template | Capability with logic | Full AI assistant |
| Arguments | Yes ($1, $2, $ARGUMENTS) | N/A | N/A |
| File access | Yes (@file) | Via tools | Via tools |
| Bash exec | Yes (!command) | Via tools | Via tools |
| Use case | Quick prompts, workflows | Autonomous features | Domain expertise |
When to use Commands: Reusable prompts, quick text expansion, parametrized instructions, file processing workflows
Command Structure
Basic Command (Prompt only)
Please review this code for security vulnerabilities and provide
specific recommendations for improvement.
File: .claude/commands/security-review.md
Usage: /security-review
Command with Frontmatter
---
description: Review code for security vulnerabilities with OWASP focus
argument-hint: [file-path] [--strict]
allowed-tools: Read, Grep, Glob
model: opus
disable-model-invocation: false
---
Please perform a comprehensive security audit of the codebase, focusing on:
- OWASP Top 10 vulnerabilities
- Authentication and authorization issues
- Input validation and sanitization
- Secrets exposure
Frontmatter Fields
All frontmatter fields are optional.
description
Brief explanation shown in /help and for SlashCommand tool.
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 · 721 lines · 85 tokens per session scan A 360fb5eefebd
command-dev is a skill published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed 5d ago), licensed MIT. It adds 85 tokens to every session and 3,410 once invoked, about $0.0003 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-30.
Other skills, from other repositories
ccc-tuneup
Audit and safely optimize the local Commander setup: version freshness, junk, count drift, superseded agents, hooks, settings keys, MCP staleness and cost settings. Read-only scan first; backs up, archives (never deletes) and asks before any fix. Use when the setup feels cluttered, stale or slow.
ccc-adopt
Merge Commander's orchestrator/executor section and a stack-tailored skill and agent list into an existing project's CLAUDE.md as a delimited, re-runnable block, with backup and diff approval first. Use when adopting Commander conventions in a repo you already have.
ccc-fable
Arm, check, audit or disarm the Fable Method: the PM loop, 12 checkable gates, workflow-first posture and verifier separation, persisted in Commander state. Use when the user says fable on/off/status/audit or wants verification-gated, orchestrated work.
ccc-codex
Manage the OpenAI Codex CLI: doctor, models, plugins, MCP servers, custom agents, cloud tasks, remote control, reviews, updates, import and config, backing up config first. Use when the user asks to check, set up or manage Codex.
ccc-deploy-check
Pre-deploy readiness gate: tests, build, debug logs, secrets, TODOs, lockfile and destructive-migration checks with a GO, CAUTION or NO-GO verdict, plus risk and rollback plan in power mode. Use when asking ready to ship, should I deploy, is it safe, deploy check, or pre-deploy.
ccc-deploy
Deploy the current build to Vercel, Fly.io, Cloudflare, GitHub Pages, npm, or a package deploy script, verify the live URL, and draft post-deploy notes. Use when a build is ready to go live or the user says deploy, push to production, or publish the package.