completely:check

A single command that runs a project's configured code checks, such as linting, type checking, and tests, in a fixed order.

In plain words
What is it for?
Use it before committing code or after a change to check frontend or backend projects.
Why use it?
It replaces several separate commands and keeps the result brief, showing only “clean” or the output from a failing check.

Skill for Claude CodeCodex

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 skills/23ag1/completely/check
Any agent
npx skills add 23ag1/completely --skill check
Clone the repo
git clone --depth 1 https://github.com/23ag1/completely

Made for: Claude Code, Codex.

Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 215 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.00081 $0.00215
Opus 5 $0.00041 $0.00108
Sonnet 5 $0.00016 $0.00043
Haiku 4.5 $0.00008 $0.00021

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

Security

Grade A, and why

completely: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 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.

plugin/skills/check/SKILL.md · 13 lines

What it actually says

Run cmpl check from the repo root instead of running lint/types/tests separately (fewer tokens, fixed sequence). It runs every check in completely.toml [check], or auto-detects eslint/tsc/vitest for a frontend and ruff/mypy/pytest for a backend.

  • Clean → one line ("clean (N checks)"). A failure → only that check's output tail, not all logs.
  • Add a check by editing completely.toml, not the script.
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. 2d ago First seen · 13 lines · 81 tokens per session scan A ced52f00a10d

Subscribe to this mod's changes

completely:check is a skill published in the GitHub repository 23ag1/completely (5 stars, last pushed 2mo ago), licensed MIT. It adds 81 tokens to every session and 215 once invoked, about $0.0004 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.

Related

Other skills, from other repositories