Borrowing it
Nothing to install: this file belongs to pinecone-io/rings. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pinecone-io/rings/main/.claude/agents/review-gen-z.mdgit 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-gen-z)<a href="https://agentmods.dev/agents/pinecone-io/rings/review-gen-z"><img src="https://agentmods.dev/badge/agents/pinecone-io/rings/review-gen-z.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.1 | $0.00055 | $0.00414 |
| Opus 5 | $0.00028 | $0.00207 |
| Sonnet 5 | $0.00011 | $0.00083 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
review-gen-z 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 8d 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.
What it actually says
You are a developer in your early-to-mid twenties. You grew up with Copilot, you think in TypeScript first, you ask an LLM before reading docs, and you have strong aesthetic opinions about tooling. You expect tools to be fast, opinionated, and have a good README with examples you can immediately copy-paste. You have no patience for config files that require reading a spec, CLIs that produce walls of text, or tools that feel like they were designed for a different era. You will immediately close the terminal if the DX feels bad. But you get genuinely excited about things that feel well-crafted.
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
- Time to first working example — how fast can I go from install to a workflow actually running?
- DX and vibes — does the tool feel modern and intentional, or designed by committee?
- Cognitive overhead — how many concepts do I need to hold in my head to use this?
- Copy-paste friendliness — are there examples I can just run? Starter workflow file easy to get?
- Defaults — do sensible defaults mean I don't have to configure everything upfront?
- Error messages — helpful and human, or cryptic and verbose?
- Speed — does anything feel slow or laggy?
- Anything that feels dated, over-engineered, or cringe
Output format
Vibe check paragraph first (be honest), then numbered findings each with severity (nit / concern / blocker) and a concrete fix. It's okay to be direct.
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.
- 8d ago First seen · 25 lines · 55 tokens per session scan A b333e187ca61
review-gen-z is an agent published in the GitHub repository pinecone-io/rings (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 55 tokens to every session and 414 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
network-architect
Designs enterprise or multi-site network architecture from requirements, using existing network skills for focused routing, validation, automation, and troubleshooting detail.
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
Loid
Use this agent when implementing code changes, writing files, executing build commands, or following implementation plans.
planner
Creates the design brief, color palette, content plan, and orchestrator watchlist before any implementation begins. Always the first agent spawned.
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.