check

check is a command for coding agents from rikdc/ai-skills. It costs 10 tokens per session (279 once invoked), scanned A, original, MPL-2.0.

A command that examines a project for code-quality problems and fixes them. Code quality checks commonly include linting, formatting, tests, builds, and security issues.

In plain words
What is it for?
Use it to run parallel fixes where possible, handle dependent test or integration issues in order, and verify linters, tests, builds, and security checks.
Why use it?
It reduces the need to find and repair unrelated problems one by one, while checking that the fixes work together.

Command

Part of the code-quality plugin — 3 commands shipped together

Install

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.

agentmods
npx agentmods add commands/rikdc/ai-skills/check
Clone the repo
git clone --depth 1 https://github.com/rikdc/ai-skills

Or install code-quality, the plugin that ships this one along with the rest of its 3 commands.

Wrote 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.

agentmods badge for check

README.md
[![agentmods](https://agentmods.dev/badge/commands/rikdc/ai-skills/check.svg)](https://agentmods.dev/commands/rikdc/ai-skills/check)
Your own site
<a href="https://agentmods.dev/commands/rikdc/ai-skills/check"><img src="https://agentmods.dev/badge/commands/rikdc/ai-skills/check.svg" alt="Measured on agentmods" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 279 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00010 $0.00279
Opus 5 $0.00005 $0.00139
Sonnet 5 $0.00002 $0.00056
Haiku 4.5 $0.00001 $0.00028

Measured 4d ago against content hash 35610187d77c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 4d 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.

plugins/code-quality/commands/check.md · 42 lines

What it actually says

Code Quality Check & Auto-Fix

Comprehensive analysis and fixing of all code quality issues. This command fixes problems, not just reports them.

Workflow

  1. Analyze project and identify all issues
  2. Spawn sub-tasks for independent fixes (linting, formatting, simple tests)
  3. Handle dependencies sequentially (complex tests, integration issues)
  4. Verify all fixes work together
  5. Continue until everything passes

Sub-task Strategy

When I find multiple issues, I'll spawn parallel sub-tasks:

  • Separate sub-tasks for different directories/modules
  • Parallel execution of independent fixes (formatting, linting, simple tests)
  • Sequential handling of dependent changes
  • Coordination to prevent conflicts

Success Criteria

  • ✅ All linters pass (zero warnings)
  • ✅ All tests pass
  • ✅ All builds succeed
  • ✅ No security vulnerabilities

Execution Promise

I will work systematically through all issues, spawning sub-tasks where beneficial, and continue until every check shows ✅ PASSING.

Example: "Found 20 issues across 8 files. Spawning 3 sub-tasks: formatting fixes, linting violations, and test failures. Coordinating results and verifying integration..."

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.

  1. 4d ago First seen · 42 lines · 10 tokens per session scan A 35610187d77c

Subscribe to this mod's changes

check is a command published in the GitHub repository rikdc/ai-skills (2 stars, last pushed 3d ago), licensed MPL-2.0. It adds 10 tokens to every session and 279 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.