116 boosters for "command" — open source, verified from GitHub, ready to install
  
This booster enforces a disciplined verification workflow that prevents false success claims by requiring developers to run and confirm verification commands before marking work complete. It's essential for any development team wanting to eliminate premature PRs and false positives.
Official GitHub toolkit for Spec-Driven Development — bootstraps projects with AI-ready templates and native support for 25+ AI agents (Claude, Cursor, Windsurf, Copilot, Gemini). The Specify CLI sets up PRD/spec workflows and generates per-agent command directories.
Incident Response Commander is an expert agent that guides engineering teams through production incident management, post-mortems, and on-call process design. It's designed for SREs, incident commanders, and reliable engineering organizations seeking structured incident coordination.
Sentry booster enables developers to inspect production errors, summarize recent issues, and pull health data from Sentry via read-only API queries. Ideal for on-call engineers and DevOps teams needing quick observability access without leaving their coding environment.
Create a real CLI that future Codex threads can run by command name from any working directory. This skill is for durable tools, not one-off scripts. If a short script in the current repo solves the task, write the script there instead. Name the target tool, its source, and the first real jobs it sh
This booster enables developers and Obsidian power users to programmatically interact with their Obsidian vaults—reading, creating, and searching notes—as well as develop and debug plugins directly from the command line. It's ideal for users who want CLI-based vault automation or are building Obsidian extensions.
Provides the Hugging Face Hub CLI (`hf`) tool for downloading, uploading, and managing models, datasets, and Spaces directly from Claude Code. Essential for developers integrating Hugging Face resources into AI workflows.
A Bash CLI wrapper for the EODHD financial data API designed for OpenClaw agents, with built-in secrets management and secure deployment practices. Useful for developers building open-source integrations that need stateless API access without credential exposure.
Comprehensive quality audit system for Claude Code agents, skills, and commands. Provides quantitative scoring, comparative analysis, and production readiness grading based on industry best practices. The 16-criteria framework is derived from: 1. Claude Code Best Practices (Ultimate Guide line 4921:
  
"name": "taches-cc-resources", "description": "Curated Claude Code skills and commands for prompt engineering, MCP servers, subagents, hooks, and productivity workflows", "name": "Lex Christopherson",
RTK Optimizer automatically suggests and applies Rust Token Killer wrappers to verbose commands (like git log, find) to reduce token consumption by up to 92%, helping developers optimize costs and efficiency in Claude Code workflows.
"name": "edmunds-claude-code", "description": "Edmund's personal Claude Code setup with 14 productivity commands and 11 specialized AI agents for modern web development", "path": ".claude/commands/new-task.md",
"name": "safety-net", "description": "Block destructive git and filesystem commands before execution", "email": "jliew@420024lab.com"
Community-driven marketplace for Claude Code commands and plugins. Add this marketplace to Claude Code: Then browse and install individual plugins (commands or agents):
Use this agent when documentation in the `architecture/` directory needs to be updated or created for a specific file after implementing a feature, fix, refactor, or behavior change. Launch one instance of this agent per file that needs updating. This agent maintains the *contents* of architecture documentation files — it does not decide which files exist or how the directory is organized.\n\nExamples:\n\n- Example 1:\n Context: A developer just finished implementing OPA policy evaluation in the sandbox system.\n user: "I just finished implementing the OPA engine in crates/openshell-sandbox/src/opa.rs. Update architecture/sandbox.md to reflect the new policy evaluation flow."\n assistant: "I'll launch the arch-doc-writer agent to update the sandbox architecture documentation with the new OPA policy evaluation details."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/sandbox.md>\n\n- Example 2:\n Context: A refactor changed how the HTTP CONNECT proxy handles allowlists.\n user: "The proxy allowlist logic was refactored. Please update architecture/proxy.md."\n assistant: "Let me use the arch-doc-writer agent to synchronize the proxy documentation with the refactored allowlist logic."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/proxy.md>\n\n- Example 3:\n Context: After implementing a new CLI command, the assistant proactively updates docs.\n user: "Add a --rego-policy flag to the CLI."\n assistant: "Here is the implementation of the --rego-policy flag."\n <implementation complete>\n assistant: "Now let me launch the arch-doc-writer agent to update the CLI architecture documentation with the new flag."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/cli.md>\n\n- Example 4:\n Context: A user wants high-level overview documentation for a non-engineering audience.\n user: "Update architecture/overview.md with a non-engineer-friendly explanation of the sandbox system."\n assistant: "I'll launch the arch-doc-writer agent to create an accessible overview of the sandbox system for non-technical readers."\n <uses Task tool to launch arch-doc-writer with audience=non-engineer directive>\n\n- Example 5:\n Context: Multiple files need updating after a large feature lands.\n user: "I just landed the network namespace isolation feature. Update architecture/sandbox.md and architecture/networking.md."\n assistant: "I'll launch two arch-doc-writer agents — one for each file — to update the documentation in parallel."\n <uses Task tool to launch arch-doc-writer for architecture/sandbox.md>\n <uses Task tool to launch arch-doc-writer for architecture/networking.md>
"version": "0.25.0", "description": "Datadog API CLI with 49 command groups, 300+ subcommands. Skills and domain agents for monitoring, logs, APM, security, and infrastructure.", "email": "support@datadoghq.com"
A universal command-line client for the Model Context Protocol (MCP) that enables developers to interact with MCP servers directly from the terminal or integrate them into Claude Code mode. Developers building with MCP, AI agents, and LLM applications benefit from this tool for testing, debugging, and extending Claude's capabilities.
mq is a jq-like CLI tool for querying and transforming Markdown files, with development guidelines covering Rust conventions, project structure, and multi-platform integrations (LSP, DAP, WASM, Python). Developers building Markdown processing pipelines or contributing to the mq project benefit from these structured instructions.
A CLI skill for interacting with Obsidian vaults—read, create, search, and manage notes, tasks, and properties directly from the command line, plus plugin/theme development support. Useful for developers and power users who want to automate vault operations and debug Obsidian extensions.
A shorthand alias for the /thread command in Claude Code, providing quick access to thread management functionality for developers working with the IDE.
"description": "A virtual design team for Claude Code, Cursor, Windsurf, Gemini CLI, and Copilot — powered by Naksha. Assembles specialist roles — UI designer, UX researcher, content designer, Figma expert, data viz, email, social, motion, presentation, brand strategy, illustration, video, conversat
"name": "dotnet-claude-kit", "description": "The definitive Claude Code companion for .NET developers. 47 skills, 10 agents, 16 commands, 10 rules, 5 templates, 15 MCP tools, 7 hooks for modern .NET 10 / C# 14.", "name": "Mukesh Murugan",
