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-serialization.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-serialization)<a href="https://agentmods.dev/agents/pinecone-io/rings/impl-serialization"><img src="https://agentmods.dev/badge/agents/pinecone-io/rings/impl-serialization/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-serialization"><img src="https://agentmods.dev/badge/agents/pinecone-io/rings/impl-serialization.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.00046 | $0.00444 |
| Opus 5.5 | $0.00018 | $0.00178 |
| Sonnet 5.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 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 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.
- 2mo ago First seen · 25 lines · 46 tokens per session scan A 9ccd4eb75411
impl-serialization is an agent published in the GitHub repository pinecone-io/rings (6 stars, last pushed 25d ago), licensed Apache-2.0. It adds 46 tokens to every session and 444 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
flutter-reviewer
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
vue-reviewer
Expert Vue.js code reviewer specializing in Composition API correctness, reactivity pitfalls, component architecture, template security, and Vue-specific performance. Use for any change touching .vue, .ts/.js files with Vue imports, or Vue ecosystem code (Pinia, Vue Router, Nuxt). MUST BE USED for Vue projects.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
kotlin-reviewer
Kotlin and Android/KMP code reviewer. Reviews Kotlin code for idiomatic patterns, coroutine safety, Compose best practices, clean architecture violations, and common Android pitfalls.
security-reviewer
Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.
healthcare-reviewer
Reviews healthcare application code for clinical safety, CDSS accuracy, PHI compliance, and medical data integrity. Specialized for EMR/EHR, clinical decision support, and health information systems.