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 skills add tenequm/pond --skill pond-add-adaptergit clone --depth 1 https://github.com/tenequm/pondWrote 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/skills/tenequm/pond/pond-add-adapter)<a href="https://agentmods.dev/skills/tenequm/pond/pond-add-adapter"><img src="https://agentmods.dev/badge/skills/tenequm/pond/pond-add-adapter/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/skills/tenequm/pond/pond-add-adapter"><img src="https://agentmods.dev/badge/skills/tenequm/pond/pond-add-adapter.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.00062 | $0.05341 |
| Opus 5.5 | $0.00025 | $0.02136 |
| Sonnet 5.5 | $0.00012 | $0.01068 |
| Haiku 4.5 | $0.00006 | $0.00534 |
Grade A, and why
pond-add-adapter 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 1mo 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding a pond adapter
An adapter is a bidirectional codec between one agent's native session format and pond's canonical schema (docs/spec.md section 6). The bar it must meet: lossless capture (every source field recoverable), no synthesized values, additive re-sync, and a restore face that is either lossless-native or an honest refusal. The registry cost is fixed and small: one file under packages/pond/src/adapter/ plus its wiring in src/adapter/mod.rs - a module declaration, a re-export, and the registry() entry (spec 6.7).
The work splits into two phases. Phase A produces the spec doc and the fixture; Phase B implements from them. Ship both in ONE self-contained PR: spec doc + fixture + adapter + tests + doc rows. Opening a draft PR after Phase A, so the decision table gets reviewed before implementation, is recommended but not required.
Ground rules that override any instinct to improvise:
- docs/spec.md section 6 is the contract. The named rules cited below (
adapter-integrity-*,adapter-bounded-values,model-no-synthesis, ...) are binding, and each states WHY it exists - read the rule before deviating. cargo fmt --check,cargo clippy --all-targets -- -D warnings,cargo testgreen is the whole bar for an adapter PR. No benchmarks: adapters are import-isolated from the store and query layer (a guard test insrc/adapter/mod.rsenforces it and lists its exemptions with reasons), so an adapter cannot reach the store's write path, commit discipline, or query plans; what it can still get wrong - parse cost, emitted volume, freshness reads - is what the conformance harness and review look at.- Third-party session-search parsers (franken_agent_detection, deja-vu, ctx, ...) may be read as corroborating references, never as the authority. Their bar is a search projection; pond's is a lossless round-trip codec.
- Fixtures come from sandboxed self-capture only. Never vendor another repo's fixture, and never copy files from a real (non-sandboxed) agent home.
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.
- 1mo ago Changed 7d07f2de683c
- 1mo ago First seen · 133 lines · 62 tokens per session scan A 500c64e841ca
pond-add-adapter is a skill published in the GitHub repository tenequm/pond (89 stars, last pushed yesterday), licensed Apache-2.0. It adds 62 tokens to every session and 5,341 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-09-18.
pond-add-adapter compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| pond-add-adaptertenequm/pond | Skill | 89 | yesterday | Apache-2.0 | A | 62 | Claude Code, Codex |
| config-managerryo-ebata/cc-audit | Skill | 26 | yesterday | MIT | A | 7 | Claude Code |
| code-review-helperryo-ebata/cc-audit | Skill | 26 | yesterday | MIT | A | 13 | Claude Code |
| system-admin-helperryo-ebata/cc-audit | Skill | 26 | yesterday | MIT | A | 9 | Claude Code |
| org-update-todoszaffarano/org-mcp-server | Skill | 45 | yesterday | MIT | A | 102 | Claude Code |
| org-agendaszaffarano/org-mcp-server | Skill | 45 | yesterday | MIT | A | 120 | Claude Code |
| org-captureszaffarano/org-mcp-server | Skill | 45 | yesterday | MIT | A | 97 | Claude Code |