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 commands/yassinello/claude-plugin-prd-workflow/quality-checkgit clone --depth 1 https://github.com/Yassinello/claude-plugin-prd-workflowWrote 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/yassinello/claude-plugin-prd-workflow/quality-check)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/quality-check"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/quality-check.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.1 | $0.00008 | $0.02048 |
| Opus 5 | $0.00004 | $0.01024 |
| Sonnet 5 | $0.00002 | $0.00410 |
| Haiku 4.5 | $0.00001 | $0.00205 |
Grade A, and why
quality-check 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 6d 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Check Command
Perform comprehensive code quality analysis including linting, testing, complexity, and performance.
Purpose
Ensure code meets quality standards before PR/merge:
- Code style and linting (ESLint, Prettier)
- Test coverage and passing tests
- Code complexity metrics
- Performance benchmarks
- Documentation coverage
- Bundle size analysis
Workflow
Step 1: Determine Scope
📊 **Code Quality Check**
Scope options:
1. 🎯 Current PRD changes (git diff)
2. 📦 Entire codebase
3. 📂 Specific directory
Select scope: (1-3)
Step 2: Linting Analysis
Run configured linters:
# ESLint
npx eslint . --ext .ts,.tsx,.js,.jsx --format json
# Prettier
npx prettier --check "**/*.{ts,tsx,js,jsx,json,md}"
# TypeScript
npx tsc --noEmit
Report:
- Error count
- Warning count
- Auto-fixable issues
- Manual fixes needed
Step 3: Test Execution
Run test suites:
# Unit tests
npm test -- --coverage --json
# Integration tests (if configured)
npm run test:integration
# E2E tests (if configured)
npm run test:e2e
Analyze:
- Total tests (passed/failed)
- Coverage percentage (lines, branches, functions)
- Slow tests (>1s)
- Flaky tests
Step 4: Code Complexity Analysis
Calculate complexity metrics:
# Complexity analysis (using eslint-plugin-complexity)
npx eslint . --rule 'complexity: [error, 10]' --format json
Report:
- Average cyclomatic complexity
- Functions exceeding threshold (>15)
- Most complex functions (top 10)
- Suggested refactoring targets
Step 5: Performance Metrics
Analyze bundle size and performance:
# Bundle size
npm run build
npx bundlesize
# Type check performance
time npx tsc --noEmit
Report:
- Bundle size (current vs target)
- Largest dependencies
- Build time
- Type check time
Step 6: Documentation Coverage
Check documentation:
- JSDoc coverage for public APIs
- README completeness
- Component stories (Storybook)
- API documentation
- Migration guides (if breaking 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.
- 6d ago First seen · 350 lines · 8 tokens per session scan A cc3daa23fced
quality-check is a command published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 8 tokens to every session and 2,048 once invoked, about $0.0000 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 commands, from other repositories
debug
Systematic debugging: root cause before any fix, one hypothesis at a time, and a three-strikes rule that questions the architecture instead of stacking patches.
lint
The canonical linter per ecosystem over your changes: findings are diagnoses you judge, fix, or explain.
verify
让 agent 重新核对最近回复中的所有 file:line 引用与事实性陈述，并报告漂移/缺失。.
logic-fix-all
Autonomous audit-and-fix — after consent, scan the target, fix every logic issue found (all severities), verify each fix, and report anything unresolved.
logic-health
Sweep a whole codebase or directory for logic correctness — use before a release or to identify risk hotspots.
logic-locate
Locate the root cause of a confirmed failure — use when you have a stack trace, failing test, or wrong output.