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 agentmods add commands/awattar/claude-code-best-practices/help-commandsgit clone --depth 1 https://github.com/awattar/claude-code-best-practicesWrote 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/awattar/claude-code-best-practices/help-commands)<a href="https://agentmods.dev/commands/awattar/claude-code-best-practices/help-commands"><img src="https://agentmods.dev/badge/commands/awattar/claude-code-best-practices/help-commands.svg" alt="Measured on agentmods" 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 | $0.00010 | $0.01318 |
| Opus 5 | $0.00005 | $0.00659 |
| Sonnet 5 | $0.00002 | $0.00264 |
| Haiku 4.5 | $0.00001 | $0.00132 |
Grade A, and why
help-commands 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 4d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code User Command: Help Commands
This command provides comprehensive help for all available custom commands in this Claude Code Best Practices repository.
Usage
To get help with available commands, just type:
/help-commands
Available Commands
/custom-init- CLAUDE.md Generator./commit- Conventional Commits./issue- GitHub Issue Workflow./reviewpr- Pull Request Review./test- Test Suite Management.
How It Works
/custom-init - CLAUDE.md Generator
- Purpose: Automatically generates comprehensive CLAUDE.md files for any project.
- Usage:
/custom-init - What it does:
- Analyzes project structure and detects technology stack.
- Generates documentation sections (Overview, Architecture, Features).
- Creates development workflow guides.
- Produces comprehensive project context for AI assistants.
- Best for: New projects, onboarding, or updating existing documentation.
/commit - Conventional Commits
- Purpose: Creates well-formatted conventional commits following best practices.
- Usage:
/commit - What it does:
- Analyzes staged changes (or stages all changes if none staged).
- Generates conventional commit messages.
- Suggests splitting large commits into smaller, atomic ones.
- Follows format:
<type>: <github_issue> - <description>.
- Best for: Maintaining clean git history and following team conventions.
/issue - GitHub Issue Workflow
- Purpose: End-to-end GitHub issue resolution following GitHub Flow.
- Usage:
/issue <issue-number> - What it does:
- Analyzes GitHub issues using
ghCLI. - Creates development plans and feature branches.
- Implements solutions with incremental commits.
- Handles testing and PR creation.
- Analyzes GitHub issues using
- Best for: Structured issue resolution and feature development.
/reviewpr - Pull Request Review
- Purpose: Comprehensive PR review process with quality checks.
- Usage:
/reviewpr <pr-number> - What it does:
- Fetches PR details and analyzes changes.
- Checks CI/CD status and code quality.
- Reviews observability, testing, and documentation.
- Provides structured feedback via GitHub CLI.
- Best for: Code reviews, quality assurance, and team collaboration.
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.
- 4d ago First seen · 154 lines · 10 tokens per session scan A 61594a97fb6a
help-commands is a command published in the GitHub repository awattar/claude-code-best-practices (251 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 1,318 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.