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.
git clone --depth 1 https://github.com/superbenefit/sb-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/commands/superbenefit/sb-marketplace/dev)<a href="https://agentmods.dev/commands/superbenefit/sb-marketplace/dev"><img src="https://agentmods.dev/badge/commands/superbenefit/sb-marketplace/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/commands/superbenefit/sb-marketplace/dev"><img src="https://agentmods.dev/badge/commands/superbenefit/sb-marketplace/dev.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.00020 | $0.01542 |
| Opus 5.5 | $0.00008 | $0.00617 |
| Sonnet 5.5 | $0.00004 | $0.00308 |
| Haiku 4.5 | $0.00002 | $0.00154 |
Grade A, and why
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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dev Command
The primary development command for Astro and Starlight projects. Handles everything from simple components to complex features with intelligent validation.
Usage
/dev [description of what to build]
/dev [description] --audit=off # Skip validation
/dev [description] --audit=light # Quick validation (5 checks)
/dev [description] --audit=comprehensive # Full validation (50+ checks)
Description
The /dev command loads the astro-coding skill (best practices, patterns, critical rules) and implements your request. It automatically validates code based on task complexity, or you can control validation with the --audit flag.
What It Does
- Understands Your Request: Analyzes what needs to be built
- Loads Relevant Patterns: Brings in only the patterns you need (components, routes, collections, etc.)
- Implements Code: Writes clean, standards-compliant Astro/Starlight code
- Validates: Checks against critical rules and best practices
- Returns Result: Complete implementation ready to use
Examples
Create a Component
/dev Add a Footer component with social links and copyright
Result: Footer.astro with proper TypeScript types, accessibility, and styling
Build a Feature
/dev Add a blog with categories and pagination
Result: Content collection, dynamic routes, category pages, pagination component
Fix Issues
/dev Fix all TypeScript errors in the components folder
Result: All type errors resolved following Astro best practices
Complex Implementation
/dev Create a multi-language content system with external data integration
Result: Custom loaders, i18n routing, data transformation, full implementation
Configuration
/dev Add Tailwind CSS integration to the project
Result: Updated astro.config with Tailwind, installed packages, example styles
Auto-Validation
By default, /dev validates your code automatically:
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 · 244 lines · 20 tokens per session scan A 6eaa90a024df
dev is a command published in the GitHub repository superbenefit/sb-marketplace (5 stars, last pushed 8mo ago), licensed CC0-1.0. It adds 20 tokens to every session and 1,542 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.