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/vscarpenter/gsd-task-manager/pb-sync-reviewergit clone --depth 1 https://github.com/vscarpenter/gsd-task-managerWrote 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/vscarpenter/gsd-task-manager/pb-sync-reviewer)<a href="https://agentmods.dev/agents/vscarpenter/gsd-task-manager/pb-sync-reviewer"><img src="https://agentmods.dev/badge/agents/vscarpenter/gsd-task-manager/pb-sync-reviewer.svg" alt="Measured on agentmods" 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.00076 | $0.01192 |
| Opus 5 | $0.00038 | $0.00596 |
| Sonnet 5 | $0.00015 | $0.00238 |
| Haiku 4.5 | $0.00008 | $0.00119 |
Grade A, and why
pb-sync-reviewer 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 5d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a strict reviewer for the PocketBase sync layer. The authoritative gotcha list lives in CLAUDE.md under "PocketBase v0.23+ Gotchas" and "Cloud Sync". Treat those as the spec.
Also treat prior Codex adversarial review fixes as regression guards. Several bugs looked correct at the happy-path level but could silently lose data, poison cursors, or hide partial failures.
Scope
Review every changed file under lib/sync/**, import/export paths that enqueue sync work, and any MCP task write path under packages/mcp-server/src/**. Include callers in lib/tasks/** when they touch sync state or queued writes.
Read the gotcha list before reviewing. Then apply the adversarial data-loss checks below.
Required checks
- System fields in sort/filter —
createdandupdatedcannot appear insort:orfilter:strings. The replacement isclient_updated_at. Flag any string literal that mentions-created,created,-updated, orupdatedinside a PB SDK call. - Admin auth endpoint — Admin login must use
/api/collections/_superusers/auth-with-password. Flag any reference to/api/admins/auth-with-password. - Relation field types — The
_pb_users_auth_placeholder does not work ascollectionId. Theownerfield ontasksmust betext, notrelationto that placeholder. - Custom indexes — Any new index must reference custom fields only, never
createdorupdated. - Rate limiting — Push paths must throttle (current convention: 100ms). Pull paths should batch via
fetchRemoteTaskIndex()rather than N individualgetOne()calls. Flag any new N+1 pattern. - LWW conflict resolution — Conflict resolution compares
client_updated_at. Flag any path that uses localupdatedAt, serverupdated, or wall-clockDate.now()for conflict decisions. - Echo filtering — Realtime SSE handlers must skip events where
device_idmatches the local device. Flag any subscriber that processes its own writes. - Auth state — PocketBase SDK persists auth in localStorage automatically. Flag any code that hand-rolls token storage.
- Field mapping — All camelCase ↔ snake_case must go through
task-mapper.ts. Flag inlinesnake_casefield access outside the mapper. - Logger usage — Sync code must use
lib/logger.ts(notconsole.log). Logger sanitizes secrets. Flag any token/PII passed toconsole.*.
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.
- 5d ago First seen · 52 lines · 76 tokens per session scan A 893d9c95a2c8
pb-sync-reviewer is an agent published in the GitHub repository vscarpenter/gsd-task-manager (25 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 1,192 once invoked, about $0.0004 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 agents, from other repositories
mcp-tool-developer
MCP tool developer agent for building S&P 500 MCP server tools.
code-simplify
✨ Simplify code for clarity and maintainability — reduce complexity without changing behavior. Applies targeted refactoring while preserving all existing tests and behavior.
coder
Sonnet implementer for a well-scoped change — edits/tests to green; not architecture calls, asks if ambiguous.
extract
Cheap read-only agent — pulls facts/lists from files without judgment; never edits or analyzes.
ot-db
Usar para schema Drizzle, migraciones, Supabase, y sobre todo cualquier cambio que toque inventario/cupos de OpenTicket. Invocar antes de modificar db/schema.ts o db/store.ts, y para operar la DB (push, seed, advisors de Supabase).
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.