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 skills add dykyi-roman/awesome-claude-code --skill check-commentsgit clone --depth 1 https://github.com/dykyi-roman/awesome-claude-codeWrote 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/skills/dykyi-roman/awesome-claude-code/check-comments)<a href="https://agentmods.dev/skills/dykyi-roman/awesome-claude-code/check-comments"><img src="https://agentmods.dev/badge/skills/dykyi-roman/awesome-claude-code/check-comments.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.01399 |
| Opus 5 | $0.00016 | $0.00700 |
| Sonnet 5 | $0.00006 | $0.00280 |
| Haiku 4.5 | $0.00003 | $0.00140 |
Grade A, and why
check-comments 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comment Quality Check
Analyze PHP code for documentation and comment issues.
Detection Patterns
1. Missing PHPDoc
// BAD: No documentation on public method
public function process(array $items, bool $force = false): Result
{
}
// GOOD: Documented public method
/**
* Process items with optional force flag.
*
* @param array<Item> $items Items to process
* @param bool $force Force processing even if already processed
* @return Result Processing result with status and errors
*
* @throws ProcessingException When processing fails
*/
public function process(array $items, bool $force = false): Result
{
}
2. Outdated Comments
// BAD: Comment doesn't match code
// Calculates the discount percentage
public function calculateTax(Money $amount): Money
{
return $amount->multiply(0.21);
}
// BAD: TODO that's been done or is stale
// TODO: Add validation (added 3 years ago)
$this->validate($data);
// BAD: Incorrect parameter documentation
/**
* @param string $userId The user ID // Actually int
*/
public function findUser(int $userId): User {}
3. Commented-Out Code
// BAD: Dead code cluttering the file
public function process(Order $order): void
{
// $this->legacyProcessor->process($order);
// if ($order->needsSpecialHandling()) {
// $this->specialHandler->handle($order);
// }
$this->newProcessor->process($order);
}
// Remove commented code - use version control instead
public function process(Order $order): void
{
$this->newProcessor->process($order);
}
4. Obvious Comments
// BAD: Comments stating the obvious
// Get the user
$user = $this->getUser();
// Increment counter
$counter++;
// Loop through items
foreach ($items as $item) {}
// GOOD: Comments explaining WHY
// Fetch fresh user to ensure permissions are current
$user = $this->getUser();
5. Self-Documenting Code Opportunities
// BAD: Comment needed due to unclear code
// Check if user can access premium features
if ($user->level >= 3 && $user->subscription !== null && $user->subscription->isActive()) {}
// GOOD: Self-documenting
if ($user->canAccessPremiumFeatures()) {}
// BAD: Magic number with comment
// 86400 seconds in a day
$expiry = time() + 86400;
// GOOD: Named constant
$expiry = time() + self::SECONDS_PER_DAY;
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 · 260 lines · 32 tokens per session scan A e6cb69ad415e
check-comments is a skill published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 22d ago), licensed MIT. It adds 32 tokens to every session and 1,399 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
php-best-practices
PHP 8.x modern patterns, PSR standards, and SOLID principles. Use when reviewing PHP code, checking type safety, auditing code quality, or ensuring PHP best practices. Triggers on "review PHP", "check PHP code", "audit PHP", or "PHP best practices".
laravel-audit-architecture
Audit a Laravel application's architecture: boundaries, responsibility, coupling, duplication, and maintainability. Use when auditing architecture.
laravel-audit-conventions
Audit a Laravel application for framework conventions: anti-patterns, version-appropriate APIs, and misuse of framework features. Use when auditing Laravel conventions.
code-quality
PHP and Laravel code quality toolchain — static analysis with Larastan/PHPStan, code style enforcement with Pint, automated refactoring with Rector, baseline management for legacy codebases, and CI pipeline integration via GitHub Actions. Use this skill whenever the user asks to check code quality, fix linting errors…
php-best-practices
PHP modernization, refactoring, code review, and standards enforcement assistant for PHP 8.2+ projects. Use this skill whenever the user wants to modernize legacy PHP code, refactor messy classes or controllers, review code for smells and anti-patterns, enforce PSR-12 and strict typing standards, or integrate Rector…
wp-phpcs-coding-standards
Set up and run PHPCodeSniffer with the WordPress Coding Standards (WPCS) and PHPCompatibility on a plugin or theme. Covers the composer dev-dependencies and their exact (and confusingly-named) packages — squizlabs/phpcodesniffer, wp-coding-standards/wpcs, phpcompatibility/phpcompatibility-wp…