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/achitokun14/claude-universal/critgit clone --depth 1 https://github.com/Achitokun14/claude-universalWrote 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/commands/achitokun14/claude-universal/crit)<a href="https://agentmods.dev/commands/achitokun14/claude-universal/crit"><img src="https://agentmods.dev/badge/commands/achitokun14/claude-universal/crit.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.00452 |
| Opus 5 | $0.00014 | $0.00226 |
| Sonnet 5 | $0.00005 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
crit 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 5d 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
Get second opinions from other AI coding tools installed on this machine.
Steps:
-
If
$ARGUMENTSis empty, ask: "What should I crit? (file path, PR description, or plain-text decision)". -
Prepare the review prompt:
Give a critical, adversarial review of the following. Call out bugs, security issues, design flaws, and simpler alternatives. Do not be polite — be useful. Under 250 words. <CONTENT>If
$ARGUMENTSis a file path, Read it and embed. If a URL, WebFetch it. Otherwise use it verbatim. -
Check availability of external reviewers with Bash:
command -v kimi→ runkimi -p "<prompt>"in background via run_in_backgroundcommand -v opencode→ runopencode run "<prompt>"command -v codex→ runcodex exec "<prompt>"command -v aider→ skip (interactive only) Dispatch all available in parallel. Skip silently if a tool is missing.
-
Also generate Claude's own review so there are always ≥2 opinions.
-
Synthesize into:
# Crit: <short title> ## Claude (self) <review> ## Kimi <review or "not installed"> ## OpenCode <review or "not installed"> ## Codex <review or "not installed"> ## Consensus - **All agree:** <shared concerns> - **Claude unique:** <only Claude flagged> - **Others unique:** <only external tools flagged> ## Recommendation <what to act on first> -
If any external tool returned nothing or errored, note it but don't fail the command.
Never pipe secrets or .env contents into external tools.
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.
- 5d ago First seen · 58 lines · 27 tokens per session scan A 63a712805649
crit is a command published in the GitHub repository Achitokun14/claude-universal (2 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 452 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
dev-screenshot
Use the dev screenshot script to iterate on UI changes. This builds the Go server with dev tags, starts it on an isolated port, opens the browser, and captures a screenshot for visual verification.
publish
Publish a new release of Coral to PyPI. The user provides the version number as $ARGUMENTS (e.g. "2.2.0").
init
Initialize configurations for Supabase local development.
milestone-list
PitWay: List every milestone with a concise one-line status.
setup
Install the claude-pace statusline bundled with this plugin.
fix
Universal debugging and fix application with semantic code analysis.