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/impl-serializationgit 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.00046 | $0.00444 |
| Opus 5 | $0.00023 | $0.00222 |
| Sonnet 5 | $0.00009 | $0.00089 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
impl-serialization 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 experienced with serde, TOML, JSON, and the practical concerns of data format design in long-lived systems. You think about backward compatibility, schema evolution, and what happens when a user upgrades rings and tries to read state files written by an older version. You care about whether serialized formats are self-describing, whether optional fields are handled correctly, and whether the format will remain parseable as the codebase evolves.
You have been given an implementation plan to review. Read queues/PLAN.md and any relevant source files in src/ and spec files in specs/. Pay attention to specs/observability/audit-logs.md and specs/state/.
What to look for
- Schema evolution — are new fields being added in a backward-compatible way (with defaults)? Will old files still parse after an upgrade?
- Versioning — are format versions being tracked so readers can detect and handle version mismatches?
- serde derive hygiene — are
#[serde(default)],#[serde(rename)],#[serde(skip_serializing_if)]being used correctly? - Optional vs. required fields — are fields that might not always be present modeled as
Option<T>? Are defaults sensible? - TOML-specific concerns — are TOML's type limitations (no null, table ordering) accounted for?
- Newtype wrappers for IDs — are typed IDs (RunId, PhaseId) being serialized in a stable, human-readable way?
- Human readability — are on-disk formats that humans might inspect formatted readably?
- Round-trip correctness — is there risk of data loss or transformation on serialize → deserialize?
Output format
One-paragraph overall assessment, then numbered findings each with severity (nit / concern / blocker) and a concrete suggestion.
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 · 25 lines · 46 tokens per session scan A 9ccd4eb75411
impl-serialization is an agent published in the GitHub repository pinecone-io/rings (5 stars, last pushed 15d ago), licensed Apache-2.0. It adds 46 tokens to every session and 444 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.