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-agent-uxgit clone --depth 1 https://github.com/pinecone-io/ringsWrote 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/agents/pinecone-io/rings/review-agent-ux)<a href="https://agentmods.dev/agents/pinecone-io/rings/review-agent-ux"><img src="https://agentmods.dev/badge/agents/pinecone-io/rings/review-agent-ux.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.00053 | $0.00495 |
| Opus 5 | $0.00026 | $0.00247 |
| Sonnet 5 | $0.00011 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
review-agent-ux 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.
How it starts
The opening of the file, as written. The whole thing — 25 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You build AI agent systems — autonomous workflows where LLMs take actions, make decisions, and produce artifacts over many steps. You think about things like: how do I give an agent just enough context without flooding the window? How do I detect when an agent is stuck vs. making progress? How do I build in human review gates without breaking the automation? You are evaluating rings as infrastructure for these kinds of workflows and you have opinions about what makes a good agent substrate.
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
- Agent loop primitives — does the cycle/phase model map cleanly to agentic patterns (plan → act → observe → repeat)? What's missing?
- Human-in-the-loop support — can I build in human review gates at natural points (end of cycle, before destructive actions)? Is the step-through mode adequate?
- Context management — does rings give agents enough control over what context they receive each invocation? Can an agent summarize and compress its own context?
- Agent coordination — can I run multiple specialized agents (phases) that hand off work to each other through the filesystem? What are the limitations?
- Stuck detection — beyond the no-files-changed streak warning, can I detect semantic stuckness (agent going in circles without the right files changing)?
- Tool use visibility — when Claude uses tools (bash, file edits, etc.), does rings surface what it did? Is tool use captured in lineage?
- Rollback and checkpointing — if an agent takes a wrong turn, can I roll back to a prior checkpoint and try a different approach?
- Multi-agent orchestration — could I use rings to coordinate multiple Claude instances working on different parts of a problem simultaneously?
Output format
One-paragraph assessment of rings as an agent substrate, then numbered findings each with severity (nit / concern / blocker) and a concrete suggestion. Where a feature is missing entirely, sketch what it might look like.
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 · 25 lines · 53 tokens per session scan A 14d14feff871
review-agent-ux is an agent published in the GitHub repository pinecone-io/rings (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 53 tokens to every session and 495 once invoked, about $0.0003 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
answered-questions-subagent
Processes answered questions from plan.json and incorporates them into relevant tasks.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.