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/centminmod/my-claude-code-setup/check-best-practicesgit clone --depth 1 https://github.com/centminmod/my-claude-code-setupWrote 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/centminmod/my-claude-code-setup/check-best-practices)<a href="https://agentmods.dev/commands/centminmod/my-claude-code-setup/check-best-practices"><img src="https://agentmods.dev/badge/commands/centminmod/my-claude-code-setup/check-best-practices.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.00000 | $0.00688 |
| Opus 5 | $0.00000 | $0.00344 |
| Sonnet 5 | $0.00000 | $0.00138 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
check-best-practices 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Best Practices
Analyze code against language-specific best practices, coding standards, and community conventions to improve code quality and maintainability.
Usage Examples
Basic Usage
"Check if this code follows Python best practices" "Review JavaScript code for ES6+ best practices" "Analyze React components for best practices"
Specific Checks
"Check if this follows PEP 8 conventions" "Review TypeScript code for proper type usage" "Verify REST API design best practices" "Check Git commit message conventions"
Instructions for Claude
When checking best practices:
- Identify Language/Framework: Detect the languages and frameworks being used
- Apply Relevant Standards: Use appropriate style guides and conventions
- Context Awareness: Consider project-specific patterns and existing conventions
- Actionable Feedback: Provide specific examples of improvements
- Prioritize Issues: Focus on impactful improvements over nitpicks
Language-Specific Guidelines
Python
- PEP 8 style guide compliance
- PEP 484 type hints usage
- Pythonic idioms and patterns
- Proper exception handling
- Module and package structure
JavaScript/TypeScript
- Modern ES6+ features usage
- Async/await over callbacks
- Proper error handling
- Module organization
- TypeScript strict mode compliance
React/Vue/Angular
- Component structure and organization
- State management patterns
- Performance optimizations
- Accessibility considerations
- Testing patterns
API Design
- RESTful conventions
- Consistent naming patterns
- Proper HTTP status codes
- API versioning strategy
- Documentation standards
Code Quality Aspects
Naming Conventions
- Variable and function names
- Class and module names
- Consistency across codebase
- Meaningful and descriptive names
Code Organization
- File and folder structure
- Separation of concerns
- DRY (Don't Repeat Yourself)
- Single Responsibility Principle
- Modular design
Error Handling
- Comprehensive error catching
- Meaningful error messages
- Proper logging practices
- Graceful degradation
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 · 136 lines · 0 tokens per session scan A 9f00d8cdeea9
check-best-practices is a command published in the GitHub repository centminmod/my-claude-code-setup (2,614 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 688 tokens. 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
sp.reverse-engineer
Reverse engineer a codebase into SDD-RI artifacts (spec, plan, tasks, intelligence).
sp.checklist
Generate a custom checklist for the current feature based on user requirements.
sp.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.
sp.specify
Create or update the feature specification from a natural language feature description.
sp.git.commit_pr
An autonomous Git agent that intelligently executes git workflows. Your task is to intelligently executes git workflows to commit the work and create PR.
sp.adr
Review planning artifacts for architecturally significant decisions and create ADRs.