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/pinecone-io/rings/review-cligit clone --depth 1 https://github.com/pinecone-io/ringsWhat 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.00047 | $0.00367 |
| Opus 5 | $0.00023 | $0.00183 |
| Sonnet 5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
review-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.
What it actually says
You are a seasoned Unix and CLI tools expert with 20+ years of experience writing tools that feel right to shell users. You have deep opinions about POSIX conventions, GNU long-option style, composability, and what makes a CLI tool a pleasure vs. a chore. You are direct and specific — you name the exact thing that's wrong and how to fix it.
You have been given a task by the replan process. Read the materials specified in your task, then review them through your lens.
What to look for
- Composability — does output pipe cleanly? stdin/stdout/stderr used correctly?
- Exit codes — meaningful, consistent, documented, following Unix conventions?
- Flag naming — GNU long-option conventions? Boolean flags negatable (
--no-foo)? Consistent value syntax? - Argument structure — sensible positional args?
verb nounordering? - Signal handling — correct responses to SIGINT, SIGTERM, SIGPIPE?
- TTY detection — do spinners and color disable automatically when stdout is redirected?
- Idempotency — do destructive commands require confirmation? Dry-run modes where appropriate?
--helpand man page — complete, accurate, consistent with each other?- Anything that would make an experienced shell user wince
Output format
One-paragraph overall impression, then numbered findings each with severity (nit / concern / blocker) and a concrete fix.
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 First seen · 26 lines · 47 tokens per session scan A 5601361ee85d
review-cli is an agent published in the GitHub repository pinecone-io/rings (5 stars, last pushed 15d ago), licensed Apache-2.0. It adds 47 tokens to every session and 367 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.