Borrowing it
Nothing to install: this file belongs to finos/git-proxy. 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/finos/git-proxy/main/.agents/skills/sink-parity/SKILL.mdgit clone --depth 1 https://github.com/finos/git-proxyWrote 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/finos/git-proxy/sink-parity)<a href="https://agentmods.dev/skills/finos/git-proxy/sink-parity"><img src="https://agentmods.dev/badge/skills/finos/git-proxy/sink-parity/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/finos/git-proxy/sink-parity"><img src="https://agentmods.dev/badge/skills/finos/git-proxy/sink-parity.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.00022 | $0.01152 |
| Opus 5.5 | $0.00009 | $0.00461 |
| Sonnet 5.5 | $0.00004 | $0.00230 |
| Haiku 4.5 | $0.00002 | $0.00115 |
Grade A, and why
sink-parity 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 20d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Keep the sink backends at feature parity.
Read AGENTS.md first. It is the canonical project guide for this repository.
GitProxy persists its state through interchangeable sink backends: src/db/file (NeDB), src/db/mongo, and src/db/postgres. They all implement the Sink interface in src/db/types.ts, and deployments pick one via the sink config. A feature that exists in one backend but not the others is a bug waiting for whichever deployment uses the others.
Use this skill whenever a change touches any of:
- the
Sinkinterface or the entity classes (Repo,User, push types) insrc/db/types.ts - any backend adapter under
src/db/file,src/db/mongo, orsrc/db/postgres - the migration framework (
src/db/migrations) or the postgres schema
The contract
src/db/types.tsis the single source of truth: theSinkinterface plus the doc comments on its members define the behaviour every backend must provide. No backend implementation, mongo included, outranks the contract. A newSinkmember or entity field is not done until all three backends implement it in the same change; do not leave a backend behind for a follow-up.npm run check-types:serverenforces the interface structurally, but it cannot see semantic drift. The rest of this checklist exists for what the compiler cannot catch.
Adding or changing a Sink member
- Add the member to the
Sinkinterface with a doc comment stating its semantics (ordering, case sensitivity, empty-result shape). - Implement it in
src/db/file,src/db/mongo, andsrc/db/postgres. The doc comment on the interface member is the reference for behaviour, not any one backend: whichever implementation lands first defines the semantics, so spell them out in the doc comment and make the other backends match it. Historically most members appeared in mongo first, but new functionality can just as well start in postgres; do not assume mongo is the template. - Export it from each backend's
index.tsand wire the dispatcher insrc/db/index.ts. - Add unit tests for every backend, not just the one you started from.
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.
- 20d ago First seen · 70 lines · 22 tokens per session scan A 01f0bb9a2b33
sink-parity is a skill published in the GitHub repository finos/git-proxy (262 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 1,152 once invoked, about $0.0001 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-10-07.
Other skills, from other repositories
ring:mapping-service-resources
Mapping a Go service's Service -> Module -> Resource hierarchy for dispatch-layer registration: detects modules and per-module PostgreSQL/MongoDB/RabbitMQ resources, database names, and shared databases, generates MongoDB index migration pairs (.up.json/.down.json), detects existing Postgres migrations, emits an HTML…
fastapi-init-skill
A tool that creates a complete FastAPI web-service starting point, including database choices, login protection, file uploads, streaming responses, API documentation, and start or restart scripts.
database-expert
Advanced database design and administration for PostgreSQL, MongoDB, and Redis. Use when designing schemas, optimizing queries, managing database performance, or implementing data patterns.
database-migrator
Migrates databases between providers (Postgres, MySQL, Supabase, PlanetScale, MongoDB). Reads source schema, generates migration scripts, handles data type mapping, foreign keys, indexes, triggers, stored procedures. Validates migration with row counts and checksums. Generates migration-plan.md with step-by-step…
database-schema-designer
Designs relational and document database schemas from requirements or an existing app - tables and collections, keys, relationships, constraints, indexes driven by real query patterns, ERDs, and reversible migration scripts - with PostgreSQL (including Supabase) as the default and MySQL, SQLite, and MongoDB supported.…
agent-database-expert
Specialist subagent: Expert database architect and engineer for PostgreSQL, MongoDB, Redis, and all major databases. Use when designing schemas, optimizing queries, planning migrations, implementing caching, or troubleshooting database performance.