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.
git clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/code-analyze-quality)<a href="https://agentmods.dev/commands/matteocervelli/llms/code-analyze-quality"><img src="https://agentmods.dev/badge/commands/matteocervelli/llms/code-analyze-quality/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.
<a href="https://agentmods.dev/commands/matteocervelli/llms/code-analyze-quality"><img src="https://agentmods.dev/badge/commands/matteocervelli/llms/code-analyze-quality.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01057 |
| Opus 5.5 | $0.00000 | $0.00423 |
| Sonnet 5.5 | $0.00000 | $0.00211 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
code-analyze-quality 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 1mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{}
description: Run comprehensive code quality checks including linting, type checking, and formatting argument-hint: [language] (auto-detect if not specified)
Code Quality Check
Run comprehensive code quality checks with automatic language detection.
Supported Languages
- Python: black, flake8, mypy, pytest
- JavaScript/TypeScript: eslint, prettier, tsc
- Swift: swiftlint, swift build
- Go: gofmt, golint, go vet
- Rust: rustfmt, clippy
Usage
/code-quality # Auto-detect language
/code-quality python # Force Python checks
/code-quality js # Force JavaScript checks
/code-quality swift # Force Swift checks
What it does
- Detects project language(s) if not specified
- Runs language-specific linters
- Checks code formatting
- Runs type checking (if applicable)
- Reports all issues with line numbers
Execution
Auto-detect and run appropriate checks
!echo "🔍 Detecting project language..." !if [ -f "pyproject.toml" ] || [ -f "setup.py" ] || [ -f "requirements.txt" ]; then echo "✓ Python project detected"; fi !if [ -f "package.json" ]; then echo "✓ JavaScript/TypeScript project detected"; fi !if [ -f "Package.swift" ] || find . -name ".xcodeproj" -o -name ".xcworkspace" 2>/dev/null | grep -q .; then echo "✓ Swift project detected"; fi
Python checks
!if [ -f "pyproject.toml" ] || [ -f "setup.py" ] || [ -f "requirements.txt" ]; then echo "\n📦 Running Python quality checks..."; fi !if command -v black &> /dev/null && ([ -f "pyproject.toml" ] || [ -f "setup.py" ]); then echo "→ Formatting check (black):" && black --check . 2>&1 | head -20; fi !if command -v flake8 &> /dev/null && ([ -f "pyproject.toml" ] || [ -f "setup.py" ]); then echo "→ Linting (flake8):" && flake8 src/ tests/ 2>&1 | head -20; fi !if command -v mypy &> /dev/null && ([ -f "pyproject.toml" ] || [ -f "setup.py" ]); then echo "→ Type checking (mypy):" && mypy src/ 2>&1 | head -20; fi
JavaScript/TypeScript checks
!if [ -f "package.json" ]; then echo "\n📦 Running JavaScript/TypeScript quality checks..."; fi !if [ -f "package.json" ] && command -v npm &> /dev/null; then echo "→ Linting (eslint):" && npm run lint 2>&1 | head -20 || echo "No lint script found"; fi !if [ -f "tsconfig.json" ] && command -v tsc &> /dev/null; then echo "→ Type checking (tsc):" && tsc --noEmit 2>&1 | head -20; fi
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.
- 1mo ago First seen · 103 lines · 0 tokens per session scan A ab117fef72af
code-analyze-quality is a command published in the GitHub repository matteocervelli/llms (25 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,057 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-01.
Other commands, from other repositories
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
audio-pass
Functional audio review for implementation, mix coverage, clarity, and player feedback.
test-value-review
Use when a diff adds or changes test files, when a PR claims coverage for config, CI workflows, templates, or HTML output, or when tests look written only to satisfy a "must have tests" rule; not for Playwright selector or performance hygiene (use /playwright-review).
auditar-refactor
Invoca refactor-safety-auditor — gate canônico antes de qualquer refactor. Coleta evidências (linhas, contrato externo, coverage, mutation) e retorna veredito GO/BLOCK/WARN/GO-OVERRIDE.
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.