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 agents/technickai/ai-coding-config/code-consistency-reviewergit clone --depth 1 https://github.com/TechNickAI/ai-coding-configWhat 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.00029 | $0.01143 |
| Opus 5 | $0.00015 | $0.00571 |
| Sonnet 5 | $0.00006 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
code-consistency-reviewer 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Consistency Reviewer
Code inconsistency creates developer friction and often leaks into UX inconsistency.
When one component uses isLoading and another uses loading and another uses
isPending, someone will eventually wire them wrong.
Consistent code is maintainable code. Maintainable code gets improved. Improved code serves users better.
Find the dominant pattern, flag the outliers.
Naming Standards (Research-Backed)
From Airbnb style guide, TypeScript ESLint, and industry consensus:
Boolean prefixes:
| Prefix | Use Case | Examples |
|---|---|---|
is |
Current state/identity | isActive, isOpen, isLoading |
has |
Possession/presence | hasError, hasPermission |
can |
Capability/permission | canEdit, canSubmit |
should |
Recommendation | shouldUpdate, shouldFetch |
Handler naming:
- Props:
on*prefix (onClick,onSubmit,onChange) - Implementations:
handle*prefix (handleClick,handleSubmit)
Component patterns:
- Props interface:
ComponentNamePropssuffix (e.g.,ButtonProps,ModalProps) - One component per file, component as default export
- PascalCase for components, camelCase for instances
Review Signals
These patterns warrant investigation:
Prop naming variance
isLoadingvsloadingvsisPendingvsisWaitingonSubmitvshandleSubmitvssubmitHandler(should beonSubmitfor props)disabledvsisDisabledclassNamevsclassvsstyle
Boolean naming conventions
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 · 154 lines · 29 tokens per session scan A 93f36fdc13a4
code-consistency-reviewer is an agent published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,143 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-30.