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/joris887/exosuit/code-qualitynpx skills add joris887/exosuit --skill code-qualitygit clone --depth 1 https://github.com/joris887/exosuitWhat 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.00048 | $0.01510 |
| Opus 5 | $0.00024 | $0.00755 |
| Sonnet 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 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.
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.
- 2d ago First seen · 143 lines · 48 tokens per session scan A 3a059c67de92
code-quality is a skill published in the GitHub repository joris887/exosuit (4 stars, last pushed 13d ago), licensed MIT. It adds 48 tokens to every session and 1,510 once invoked, about $0.0002 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 skills, from other repositories
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
ship
Build, commit, push & version bump workflow - automates the complete release cycle.
pr-review
Batch review des PRs RTK par ordre de complexité croissante (XS → S → M → L). Pour chaque PR : vérifie l'état (conflits, CLA, reviews), lit le diff complet, analyse le code en contexte, présente un résumé avec lien + taille + recommandation. Attend validation explicite avant tout merge. Poste des commentaires…
rtk-triage
Triage complet RTK : exécute issue-triage + pr-triage en parallèle, puis croise les données pour détecter doubles couvertures, trous sécurité, P0 sans PR, et conflits internes. Sauvegarde dans claudedocs/RTK-YYYY-MM-DD.md. Args: "en"/"fr" pour la langue (défaut: fr), "save" pour forcer la sauvegarde.
code-simplifier
Review RTK Rust code for idiomatic simplification. Detects over-engineering, unnecessary allocations, verbose patterns. Applies Rust idioms without changing behavior.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…