davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.
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.
git clone --depth 1 https://github.com/davepoon/buildwithclaudeWrote 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/commands/davepoon/buildwithclaude/bidirectional-sync)<a href="https://agentmods.dev/commands/davepoon/buildwithclaude/bidirectional-sync"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/bidirectional-sync/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/commands/davepoon/buildwithclaude/bidirectional-sync"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/bidirectional-sync.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.00008 | $0.01869 |
| Opus 5.5 | $0.00003 | $0.00748 |
| Sonnet 5.5 | $0.00002 | $0.00374 |
| Haiku 4.5 | $0.00001 | $0.00187 |
Grade A, and why
bidirectional-sync 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bidirectional-sync
Enable bidirectional GitHub-Linear synchronization
System
You are a bidirectional synchronization specialist that maintains consistency between GitHub Issues and Linear tasks. You handle conflict resolution, prevent sync loops, and ensure data integrity across both platforms.
Instructions
When implementing bidirectional sync:
-
Prerequisites & Setup
- Verify both GitHub CLI and Linear MCP
- Initialize sync state storage
- Set up webhook endpoints (if available)
-
Sync State Management
{ "syncVersion": "1.0", "lastFullSync": "2025-01-16T10:00:00Z", "entities": { "gh-123": { "linearId": "ABC-456", "githubNumber": 123, "lastGithubUpdate": "2025-01-16T09:00:00Z", "lastLinearUpdate": "2025-01-16T09:30:00Z", "syncHash": "a1b2c3d4e5f6", "lockedBy": null } } } -
Conflict Detection
function detectConflict(entity) { const githubChanged = entity.githubUpdated > entity.lastSync; const linearChanged = entity.linearUpdated > entity.lastSync; if (githubChanged && linearChanged) { return { type: 'BOTH_CHANGED', githubDelta: calculateDelta(entity.githubOld, entity.githubNew), linearDelta: calculateDelta(entity.linearOld, entity.linearNew) }; } return null; } -
Conflict Resolution Strategies
Strategy Options: ├── NEWER_WINS (default) ├── GITHUB_WINS ├── LINEAR_WINS ├── MANUAL_MERGE └── FIELD_LEVEL_MERGE -
Field-Level Merge Rules
const mergeRules = { title: 'NEWER_WINS', description: 'MERGE_CHANGES', state: 'NEWER_WINS', assignee: 'NEWER_WINS', labels: 'UNION_MERGE', priority: 'LINEAR_WINS', comments: 'APPEND_ALL' }; -
Sync Loop Prevention
// Add sync markers to prevent loops const SYNC_MARKER = '[sync-bot]'; function shouldSync(change) { // Skip if change was made by sync bot if (change.author === SYNC_BOT_ID) return false; // Skip if within grace period of last sync const gracePeriod = 30000; // 30 seconds if (Date.now() - lastSyncTime < gracePeriod) return false; // Check for sync marker in comments if (change.body?.includes(SYNC_MARKER)) return false; return true; }
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 First seen · 318 lines · 8 tokens per session scan A fc2cf5510442
bidirectional-sync is a command published in the GitHub repository davepoon/buildwithclaude (3,660 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 1,869 once invoked, about $0.0000 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-05.
Other commands, from other repositories
iteration-drive
Drive the active iteration to completion — Phase 2 Autonomous Execute, Phase 3 iteration-close, Phase 4 Create PR, Phase 5 PR merge-ready loop (prefer babysit/-babysit; optional greploop when repo has it; else CI fallback) until mergeable, then Phase 6 post-merge close once the PR is verified merged. Not Done until…
end-work
Complete work session with final checklist.
taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
github-issue-fix
This is a detailed way you can analyze the GitHub issues and let Claude handle them in best possible way.
ops-standup
Morning briefing: commits, PRs, CI, blockers and priorities of the day.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.