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 skills/nasrulhazim/claude/code-qualitynpx skills add nasrulhazim/claude --skill code-qualitygit clone --depth 1 https://github.com/nasrulhazim/claudeWrote 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/nasrulhazim/claude/code-quality)<a href="https://agentmods.dev/skills/nasrulhazim/claude/code-quality"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/code-quality.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.00218 | $0.03881 |
| Opus 5 | $0.00109 | $0.01940 |
| Sonnet 5 | $0.00044 | $0.00776 |
| Haiku 4.5 | $0.00022 | $0.00388 |
Grade A, and why
code-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 today.
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 — 510 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Toolchain
Static analysis, code style enforcement, automated refactoring, and CI quality gates for Laravel projects. Built on top of Laravel Kickoff's existing PHPStan, Pint, Rector, and GitHub Actions configuration.
Command Reference
| Command | Description |
|---|---|
/quality check |
Run Larastan analysis, interpret errors, suggest fixes |
/quality fix |
Auto-fix Pint violations with explanations of what changed |
/quality baseline |
Generate or update PHPStan baseline for legacy code |
/quality rector |
Suggest and apply Rector rules for code modernisation |
/quality ci |
Extend GitHub Actions CI with custom quality gates |
Kickoff Baseline
Laravel Kickoff projects ship with these tools pre-configured:
| Tool | Config File | Purpose |
|---|---|---|
| PHPStan / Larastan | phpstan.neon |
Static analysis |
| Laravel Pint | pint.json |
Code style (PSR-12 / Laravel preset) |
| Rector | rector.php |
Automated refactoring |
| GitHub Actions | .github/workflows/ci.yml |
CI pipeline |
This skill extends that baseline — it does not replace it. Always read the existing config files before suggesting changes. Never overwrite without confirming with the user.
1. /quality check — Larastan Analysis
Step 1: Run Analysis
./vendor/bin/phpstan analyse --memory-limit=512M
If a baseline exists (phpstan-baseline.neon), PHPStan automatically excludes baselined
errors. Only new errors are reported.
Step 2: Interpret Errors
For each error, explain:
- What the error means in plain language
- Why PHPStan flags it (type safety, missing return, undefined method, etc.)
- How to fix it with a concrete code change
Common Error Patterns
| Error Pattern | Meaning | Fix |
|---|---|---|
Parameter #1 $x expects string, int given |
Type mismatch in function call | Cast or validate the input type |
Call to an undefined method |
Method does not exist on the resolved type | Add @method PHPDoc or fix the class reference |
Property $x has no type declaration |
Missing property type | Add typed property: public string $x; |
Method should return X but returns Y |
Return type mismatch | Fix return value or widen the return type |
Access to an undefined property |
Property not declared on the class | Declare the property or add @property PHPDoc |
Dead catch — Throwable is never thrown |
Catching an exception that cannot occur | Remove the dead catch or fix the try block |
If condition is always true/false |
Redundant conditional logic | Simplify the condition or remove dead code |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +38 lines 7d2e4c59b251
- 4d ago First seen · 472 lines · 218 tokens per session scan A e1c76ad99284
code-quality is a skill published in the GitHub repository nasrulhazim/claude (22 stars, last pushed yesterday), licensed MIT. It adds 218 tokens to every session and 3,881 once invoked, about $0.0011 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…