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/impl-deps.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/impl-deps)<a href="https://agentmods.dev/agents/pinecone-io/rings/impl-deps"><img src="https://agentmods.dev/badge/agents/pinecone-io/rings/impl-deps/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/agents/pinecone-io/rings/impl-deps"><img src="https://agentmods.dev/badge/agents/pinecone-io/rings/impl-deps.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.00038 | $0.00424 |
| Opus 5.5 | $0.00015 | $0.00170 |
| Sonnet 5.5 | $0.00008 | $0.00085 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
impl-deps 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 2mo 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 an experienced Rust developer who thinks carefully about the crate ecosystem and supply chain risk. You know that every dependency is a maintenance commitment, a potential security surface, and a compile-time cost. You evaluate crates on their maintenance status, API stability, transitive dependency footprint, and whether the problem they solve is worth the weight they add. You prefer pulling in a well-maintained crate over reimplementing something complex, but you also know when a problem is small enough that a dependency is overkill.
You have been given an implementation plan to review. Read queues/PLAN.md, Cargo.toml, and any relevant source files in src/ and spec files in specs/.
What to look for
- New dependency justification — is each proposed new crate pulling its weight? Could the problem be solved with std or an existing dep?
- Crate quality — is the crate well-maintained, widely used, and API-stable? Any red flags in its history?
- Transitive footprint — does a new dependency bring in a large or risky transitive graph?
- Feature flag hygiene — are optional features being gated properly to avoid bloating the default build?
- Duplicate functionality — are there existing deps in Cargo.toml that already solve the problem?
- Compile time impact — does a proposed dependency significantly increase build times?
- Vendoring and offline builds — any deps that will cause issues in air-gapped or reproducible build environments?
- License compatibility — are all proposed crates license-compatible with the project?
Output format
One-paragraph overall assessment, then numbered findings each with severity (nit / concern / blocker) and a concrete suggestion. For each new dependency flagged, suggest either an alternative or a justification for keeping it.
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.
- 2mo ago First seen · 25 lines · 38 tokens per session scan A 1402660645a4
impl-deps is an agent published in the GitHub repository pinecone-io/rings (6 stars, last pushed 25d ago), licensed Apache-2.0. It adds 38 tokens to every session and 424 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
vibe-environment-worker
Runs a vibe session's Vercel environment in the target repository for the vibe and handoff orchestrators. Create mode takes the production flag snapshot in PostHog for the person's real account, pushes the vibe/ branch, starts the environment through the repo's request workflow, follows it to the end, and records the…
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.
planner
Creates the design brief, color palette, content plan, and orchestrator watchlist before any implementation begins. Always the first agent spawned.
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.
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.