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 crittylabs/critty --skill critty-cligit clone --depth 1 https://github.com/crittylabs/crittyWrote 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/crittylabs/critty/critty-cli)<a href="https://agentmods.dev/skills/crittylabs/critty/critty-cli"><img src="https://agentmods.dev/badge/skills/crittylabs/critty/critty-cli/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/crittylabs/critty/critty-cli"><img src="https://agentmods.dev/badge/skills/crittylabs/critty/critty-cli.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.07810 |
| Opus 5.5 | $0.00019 | $0.03124 |
| Sonnet 5.5 | $0.00010 | $0.01562 |
| Haiku 4.5 | $0.00005 | $0.00781 |
Grade A, and why
critty-cli 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 yesterday.
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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Critty CLI Reference
Use /critty to run the interactive review loop and /critty-approval to prepare approval requests and act on their results. This reference owns command syntax, input and output formats, and local effects. Consult the sections needed for the current operation.
Local storage and command effects
Critty is a local CLI and human review TUI, not a hosted review service. Review data lives under $XDG_STATE_HOME/critty (default ~/.local/state/critty). A compatibility symlink keeps the old tcrit state path usable without moving data or active sockets. If the paths cannot be linked or contain independent directories, Critty continues using the existing legacy directory without merging or deleting either. Configuration uses $XDG_CONFIG_HOME/critty/config.json (default ~/.config/critty/config.json) and .critty.config.json in the project root. Each level reads its TCrit file only if the Critty file is absent: $XDG_CONFIG_HOME/tcrit/config.json globally, .tcrit.config.json for the project. Project settings override global settings; ignore patterns are unioned and prompt keys are merged across those two levels. Custom prompt files use .critty/prompts/ and the global critty/prompts/ directory, with the corresponding TCrit directories as lower-priority fallbacks at each level. critty install prompts writes only the Critty paths. Review processes communicate through local Unix sockets. The built-in review and comment commands do not upload review contents or publish repository changes.
| Command | Effects |
|---|---|
comments, status |
Read local review state. |
doctor (check alias) |
Compare installed integrations with embedded files and inspect local Python/MCP prerequisites and image forwarding settings, plus desktop launcher availability, Codex wrapper selection, and tfil detection for the current platform. --terminal-request ID consumes a prepared request to test terminal binding without opening a review. Desktop checks do not open windows or test automation permission. Runs bounded Python imports and an image capability probe on its foreground controlling TTY. Temporarily uses raw terminal input, then restores it; sends a transparent virtual placement, deletes it, and restores the cursor. Does not start a reviewer, contact a model or package registry, or change stored settings. |
terminal prepare |
Remove expired local marker requests, save a random marker with a two-minute expiry, and print its JSON. No review content is read and no external service is contacted. |
terminal notify |
Record a local terminal destination supplied by the terminal filter. |
review, plan, --session |
Read the selected input, save local review state, and open the human TUI, using tmux or Herdr when applicable. Terminal-marker resolution can read visible text in registered panes. |
comment |
Add or update comments in local review state; it does not post a GitHub or GitLab comment. |
stop, clear |
stop closes the review TUI and preserves saved state. clear deletes the selected saved review and attachments. |
install |
Write integration files to the selected project or user configuration directories. |
env, env tty |
Inspect local terminal/process information and print the requested environment or device. |
env run, env -- |
Execute the supplied command with the detected terminal environment. Assess that command's own effects; the wrapper does not make it read-only or local-only. |
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.
- yesterday Changed · +52 lines ab018888e328
- 2d ago Changed · +6 lines 9d341ed40c42
- 4d ago First seen · 276 lines · 48 tokens per session scan A fccdcde006c8
critty-cli is a skill published in the GitHub repository crittylabs/critty (88 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 7,810 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-10-12.
Other skills, from other repositories
pr-comments
Fetch and display GitHub PR review comments for the current branch.
simplify
Clean up changed code while preserving intended behavior. Use when the user asks to simplify or improve code quality through reuse, simplification, efficiency, and abstraction reviews. Correctness bug hunting is outside scope.
cmd-review
Review the current diff or selected files (usage: /review [instructions | --last-diff | --target | --file | files...] [--style ]).
assess-patch-risk
Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This skill is read-only and does not generate…
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
design-review
Deep design review of Go codebase — naming, structure, consistency, interfaces, error handling. Scores each dimension and provides actionable fixes.