best-practices-block

best-practices-block is a command for Claude Code from appboypov/pew-pew-plaza-packs. It costs 0 tokens per session (222 once invoked), scanned A, original, MIT.

A documentation template for listing recommended ways to build and maintain software. It can cover security, testing, performance, readability, versioning, and reviews.

In plain words
What is it for?
Use it in engineering guides, project specifications, code review checklists, and implementation plans.
Why use it?
It gathers project standards in one place so developers can apply the same expectations consistently.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it in engineering guides, project specifications, code review checklists, and implementation plans.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/appboypov/pew-pew-plaza-packs/best-practices-block
Install

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.

Clone the repo
git clone --depth 1 https://github.com/appboypov/pew-pew-plaza-packs

Made for: Claude Code.

Wrote 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.

agentmods badge for best-practices-block

README.md
[![agentmods](https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/best-practices-block/github.svg)](https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/best-practices-block)
Your own site
<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/best-practices-block"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/best-practices-block/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.

agentmods 80×15 button for best-practices-block

Your own site · 80×15
<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/best-practices-block"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/best-practices-block.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 222 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00222
Opus 5 $0.00000 $0.00111
Sonnet 5 $0.00000 $0.00044
Haiku 4.5 $0.00000 $0.00022

Measured 9d ago against content hash 447cf09faacd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

best-practices-block 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 9d 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.

.claude/commands/add/best-practices-block.md · 28 lines

What it actually says

Block Command

When this command is used, use the following block. Acknowledge your understanding and then await the user's request.


## ⭐ Best Practices
> 💡 *Industry standards and recommended approaches that should be followed.*

[List best practices with references to relevant documentation]

```
<example>
- Always follow [[solid-principles-wl-example]] for maintainable code
- Use semantic versioning as described in [[versioning-guide-wl-example]]
- Implement error handling according to [[error-handling-patterns-wl-example]]
- Apply [[security-best-practices-wl-example]] for secure implementation
- Write tests following the patterns in [[testing-standards-wl-example]]
- Keep dependencies minimal and well-documented
- Follow [[performance-optimization-guide-wl-example]] for optimal performance
- Ensure code is readable and self-documenting
- Follow [[code-review-checklist-wl-example]] before submitting PRs
- Apply [[accessibility-guidelines-wl-example]] for inclusive design
</example>
```
Changes

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.

  1. 9d ago First seen · 28 lines · 0 tokens per session scan A 447cf09faacd

Subscribe to this mod's changes

best-practices-block is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 222 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-09-03.