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 dev-toolings/superpowers-symfony --skill quality-checksgit clone --depth 1 https://github.com/dev-toolings/superpowers-symfonyWrote 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/dev-toolings/superpowers-symfony/quality-checks)<a href="https://agentmods.dev/skills/dev-toolings/superpowers-symfony/quality-checks"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/quality-checks/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/skills/dev-toolings/superpowers-symfony/quality-checks"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/quality-checks.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.00026 | $0.00358 |
| Opus 5.5 | $0.00010 | $0.00143 |
| Sonnet 5.5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
quality-checks 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 23d 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.
This is a copy
83% identical to brainstorming — 44 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Quality Checks (Symfony)
Use when
- Before committing or opening a pull request.
- Setting up or tuning PHP-CS-Fixer or PHPStan in a Symfony project.
- A CI quality job fails and the cause must be found and fixed.
Default workflow
- Detect the tools and configuration files present (
.php-cs-fixer.dist.php,phpstan.dist.neon). - Run the style fixer in dry-run with a diff first, then apply it.
- Run PHPStan at the configured level and fix the reported types.
- Run the test suite last, after style and analysis are green.
Guardrails
- Do not raise the PHPStan level or add baseline entries to make a run pass.
- Keep style-only changes in their own commit, apart from behavior changes.
- Do not silence an error with an ignore rule without a written reason.
- Use the runner the project uses (Docker or host), from the runtime context.
Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
Output contract
- The commands run and their result.
- The fixes applied, style separated from types.
- Remaining findings that need a decision.
References
reference.md
What ships with it
1 file 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.
- 23d ago Changed · +1 lines bc8e080f8f58
- 1mo ago Changed · +3 lines · -3 tokens per session 94fe366e3c36
- 1mo ago Changed · +29 tokens per session 97fb5f8e5c18
- 1mo ago First seen · 42 lines · 0 tokens per session scan A b77a95fd7d10
quality-checks is a skill published in the GitHub repository dev-toolings/superpowers-symfony (227 stars, last pushed 23d ago), licensed MIT. It adds 26 tokens to every session and 358 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to brainstorming, differing in 44 lines, and is treated as a copy.
Other skills, from other repositories
spine-review
API and backend code review — REST conventions, auth, validation, error handling, pagination, rate limiting, test coverage. Use when asked to "review this API", "code review", "review backend", or "pre-launch backend check".
github-pr-review
Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or…
superreview
Review a change set or explicit project scope for intent, correctness, safety, reuse, and maintainability; independently validate findings and produce one report without applying fixes.
init
Opt-in onboarding for the mARC agent team. Scaffolds a per-repo team binding so the team graduates from ephemeral session-memory to persistent, versioned config — without ever writing a file silently. Discovers the repo's org/repo/ project at runtime via gh, prefills {{ agentsdir }}/team.toml, and (optionally) a lean…
ccc-sol-loop
Review a change in a bounded loop with an OpenAI reviewer through the Codex CLI, answer each finding with the smallest fix, and stop at agreement or budget. Use when the user says "sol loop" or wants a second-provider review before or after a PR.
caveman-review
Ultra-compressed code review comments — one line per finding: location, problem, fix.