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/piyush8296/claude-workspace/code-qualitygit clone --depth 1 https://github.com/Piyush8296/claude-workspaceWhat 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.00010 | $0.00429 |
| Opus 5 | $0.00005 | $0.00215 |
| Sonnet 5 | $0.00002 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
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 2d 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.
What it actually says
Code Quality Review
Review code quality in: $ARGUMENTS
Instructions
1. Identify target files
Find all .ts and .tsx files in the target path. Exclude node_modules, dist, .next, and generated files (*.generated.*, *.d.ts).
2. Run automated checks
# Lint
npx eslint --no-error-on-unmatched-pattern $ARGUMENTS
# Type check
npx tsc --noEmit
# Format check (don't fix, just report)
npx prettier --check $ARGUMENTS
3. Manual review checklist
For each file, verify:
- No TypeScript
anytypes (useunknownwith type guards) - No type assertions without
// SAFETY:comment - Error handling: all
catchblocks surface feedback to user - Loading states:
isPending && !datapattern, not bareloading - Empty states: every list has an explicit empty state
- Mutations: triggers disabled during pending,
onErrorshows toast - Accessibility: semantic HTML, alt text, keyboard support
- No inline styles for layout — use Tailwind/CSS modules
- Functions under 50 lines, components under 250 lines
- Imports: no circular dependencies, no deep barrel re-exports
4. Report findings
Organize by severity:
CRITICAL (must fix before merge)
- Security vulnerabilities, data loss risks, logic errors
WARNING (should fix)
- Convention violations, accessibility gaps, missing error handling
SUGGESTION (consider improving)
- Naming, readability, minor performance gains
Include file:line references and example fixes for each finding.
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.
- 2d ago First seen · 58 lines · 10 tokens per session scan A 8b6327f4b767
code-quality is a command published in the GitHub repository Piyush8296/claude-workspace (2 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 429 once invoked, about $0.0001 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-31.
Other commands, from other repositories
review-pr
Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.
create_plan
Create detailed implementation plans through interactive research and iteration.
research_codebase
Document codebase as-is with thoughts directory for historical context.
iterate_plan
Iterate on existing implementation plans with thorough research and updates.
resume_handoff
Resume work from handoff document with context analysis and validation.
create_handoff
Create handoff document for transferring work to another session.