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.
git clone --depth 1 https://github.com/Tenon-Net/TenonAdminWrote 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/tenon-net/tenonadmin/style-reviewer)<a href="https://agentmods.dev/commands/tenon-net/tenonadmin/style-reviewer"><img src="https://agentmods.dev/badge/commands/tenon-net/tenonadmin/style-reviewer/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/commands/tenon-net/tenonadmin/style-reviewer"><img src="https://agentmods.dev/badge/commands/tenon-net/tenonadmin/style-reviewer.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.00011 | $0.01117 |
| Opus 5.5 | $0.00004 | $0.00447 |
| Sonnet 5.5 | $0.00002 | $0.00223 |
| Haiku 4.5 | $0.00001 | $0.00112 |
Grade A, and why
style-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 today.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- style-reviewer — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inconsistent style makes code harder to read and review. These rules exist because style consistency reduces cognitive load for the entire team.
<ask_gate> Do not ask for style preferences. Read config files (.eslintrc, .prettierrc, etc.) to determine project conventions. </ask_gate>
- Default to outcome-first, evidence-dense outputs; include the result, evidence, validation or uncertainty, and stop condition without padding.
- Treat newer user task updates as local overrides for the active task thread while preserving earlier non-conflicting criteria.
- If correctness depends on more reading, inspection, verification, or source gathering, keep using those tools until the review is grounded.
<execution_loop> <success_criteria>
- Project config files read first (.eslintrc, .prettierrc, etc.) to understand conventions
- Issues cite specific file:line references
- Issues distinguish auto-fixable (run prettier) from manual fixes
- Focus on CRITICAL/MAJOR violations, not trivial nitpicks </success_criteria>
<verification_loop>
- Default effort: low (fast feedback, concise output).
- Stop when all changed files are reviewed for style consistency.
- Continue through clear, low-risk next steps automatically; ask only when the next step materially changes scope or requires user preference. </verification_loop> </execution_loop>
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.
- today First seen · 103 lines · 11 tokens per session scan A 8dc0ea45e9ed
style-reviewer is a command published in the GitHub repository Tenon-Net/TenonAdmin (41 stars, last pushed 14d ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,117 once invoked, about $0.0000 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-11-07.
style-reviewer compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| style-reviewerTenon-Net/TenonAdmin | Command | 41 | 14d ago | Apache-2.0 | A | 11 | Claude Code, Codex |
| indexxberg-io/crawlberg | Command | 195 | yesterday | MIT | A | 0 | Claude Code |
| dotnet-teachmathisk2095/jko-claude-plugins | Command | 3 | 24d ago | MIT | A | 29 | Claude Code |
| dotnet-structuremathisk2095/jko-claude-plugins | Command | 3 | 24d ago | MIT | A | 24 | Claude Code |
| code-simplifypeterblazejewicz/claude-plugins | Command | 8 | 4mo ago | MIT | A | 16 | Claude Code |
| dotnet-code-reviewwgdotnet/awesome-claude-code | Command | 5 | 6mo ago | none | B | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |