Borrowing it
Nothing to install: this file belongs to tenequm/pond. 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/tenequm/pond/main/.agents/skills/add-adapter/SKILL.mdgit 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/add-adapter)<a href="https://agentmods.dev/skills/tenequm/pond/add-adapter"><img src="https://agentmods.dev/badge/skills/tenequm/pond/add-adapter.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00061 | $0.05308 |
| Opus 5 | $0.00030 | $0.02654 |
| Sonnet 5 | $0.00012 | $0.01062 |
| Haiku 4.5 | $0.00006 | $0.00531 |
Grade A, and why
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 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.
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.
- 8d ago First seen · 133 lines · 61 tokens per session scan A 2934f7972705
add-adapter is a skill published in the GitHub repository tenequm/pond (58 stars, last pushed today), licensed Apache-2.0. It adds 61 tokens to every session and 5,308 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-30.
Other skills, from other repositories
config-manager
Skill that manages configuration.
code-review-helper
A safe skill that helps with code review tasks.
org-update-todo
Update the TODO state and metadata of an existing org-mode heading via the org MCP server. Use when the user wants to change a task's state, priority, tags, or timestamps. Triggers: "mark as done", "complete this task", "reschedule", "change priority", "update the deadline", "close this TODO", "set a deadline", "retag…
org-agenda
View and manage org-mode agenda, scheduled tasks, TODOs, and deadlines via the org MCP server. Use when the user asks about their schedule, agenda, tasks, or deadlines. Triggers: "show my agenda", "what's on my schedule", "tasks for today", "tomorrow's agenda", "what do I have this week", "show next week", "last…
org-capture
Create new org-mode headings and notes via the org MCP server. Use when the user wants to add a new task, note, journal entry, or any new heading to their org files. Triggers: "add a task", "create a note", "capture this", "log an entry", "add to my notes", "create a TODO", "add a journal entry", "record this idea"…
org-search
Search and browse org-mode documents via the org MCP server. Use when the user wants to find content across org files, list their org documents, read file contents, or navigate headings and outlines. Triggers: "search my notes for...", "find org pages about...", "list my org files", "show outline of...", "read the…