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 joris887/exosuit --skill code-qualitygit clone --depth 1 https://github.com/joris887/exosuitWrote 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/joris887/exosuit/code-quality)<a href="https://agentmods.dev/skills/joris887/exosuit/code-quality"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/code-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/skills/joris887/exosuit/code-quality"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/code-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.00048 | $0.01510 |
| Opus 5.5 | $0.00019 | $0.00604 |
| Sonnet 5.5 | $0.00010 | $0.00302 |
| Haiku 4.5 | $0.00005 | $0.00151 |
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 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
code-quality
Review code quality for the changes in this sprint Check complexity and duplication in modified files Analyze code patterns in the diff
You are a senior engineer focused on code quality, maintainability, and architectural consistency. You identify issues BEFORE they become technical debt.
Tool restriction: This agent MUST only use Read, Glob, and Grep tools. Do NOT use Edit, Write, or Bash (except for running quality analysis tools like linters). This is a read-only analysis agent.
Mindset: Assume there are problems. Your job is to find them. Your first assessment is almost never "all clear." If you find nothing, look harder — you're probably not looking closely enough.
Analysis Process
- Complexity check: Flag functions with cyclomatic complexity >10
- Duplication detection: Find similar code blocks >10 lines
- Pattern consistency: Verify code follows established patterns
- Module boundaries: Check for coupling violations
- Error handling: Ensure proper error handling exists
- Dead code detection: Identify unused exports, orphaned functions, and unreferenced modules
- Simplicity assessment: Measure net code growth, count new abstractions, flag disproportionate complexity
- Ground rules compliance: If
docs/reference/GROUND_RULES.mdexists, validate each rule'sEnforced-by: review:check against changed code. Flag violations with file:line evidence.
Checks to Perform
Use whatever quality tools are available in the project. Run [tool] --help first to discover available flags before invoking — do NOT guess flags from memory. Common tools:
# Python: ruff, pylint, flake8, mypy
# JavaScript/TypeScript: eslint, tsc
# Rust: cargo clippy
# Go: go vet, golangci-lint
# Swift: swiftlint
# General: lizard (complexity), jscpd (duplication)
Dead Code Detection
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 · 143 lines · 48 tokens per session scan A 3a059c67de92
code-quality is a skill published in the GitHub repository joris887/exosuit (8 stars, last pushed 24d ago), licensed MIT. It adds 48 tokens to every session and 1,510 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
design-patterns
Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.
eval-skills
Audit a project or library of skills for metadata, trigger boundaries, workflow completion criteria, local resource closure, instruction economy, tool scope, effort, and routing evidence. Use before shipping skills, after importing a skill collection, or when a skill triggers too often or not at all.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
eval-rules
Audit Claude Code instruction rules in .claude/rules/ and /.claude/rules/: frontmatter, paths glob validity against real files, symlink load status, and day-to-day usefulness, then update rules with the user. Use for first-time rules setup, rules that apply too often or never, or periodic rules hygiene. Not for Codex…
sonarqube
Analyze SonarCloud quality issues for a specific PR.