Borrowing it
Nothing to install: this file belongs to bybren-llc/rendertrust. 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/bybren-llc/rendertrust/dev/.claude/commands/local-sync.mdgit clone --depth 1 https://github.com/bybren-llc/rendertrustWrote 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/bybren-llc/rendertrust/local-sync)<a href="https://agentmods.dev/commands/bybren-llc/rendertrust/local-sync"><img src="https://agentmods.dev/badge/commands/bybren-llc/rendertrust/local-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/bybren-llc/rendertrust/local-sync"><img src="https://agentmods.dev/badge/commands/bybren-llc/rendertrust/local-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.00007 | $0.02117 |
| Opus 5.5 | $0.00003 | $0.00847 |
| Sonnet 5.5 | $0.00001 | $0.00423 |
| Haiku 4.5 | $0.00001 | $0.00212 |
Grade C, and why
local-sync scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules This is a copy
89% identical to local-sync — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📋 TEMPLATE: This command is a template. See "Customization Guide" below to adapt for your infrastructure.
Perform complete local development environment sync after pulling from dev branch. This ensures dependencies, database, and validation are all up-to-date.
Workflow
1. Git Branch Cleanup (Best Practice)
Check current branch and switch to dev if needed:
CURRENT_BRANCH=$(git branch --show-current)
echo "Current branch: $CURRENT_BRANCH"
If on feature branch:
- Check for uncommitted changes
- If clean, switch to dev:
git checkout dev - If dirty, offer to stash:
git stash && git checkout dev - Save feature branch name for cleanup
Switch to dev branch:
git checkout dev
2. Git Pull
Pull latest changes from origin/dev:
git pull origin dev
If pull fails due to uncommitted changes:
- Stash changes:
git stash - Pull again
- Reapply stash:
git stash pop
3. Branch Cleanup (Git Best Practice)
After pulling latest dev, clean up merged branches:
Check if previous feature branch is merged:
# If we switched from a feature branch, check if it's merged
git branch --merged dev | grep -v "^\*" | grep -v "dev" | grep -v "master"
Offer to delete merged feature branch:
# Example: REN-381-rename-slash-commands-remote-prefix
git branch -d REN-381-rename-slash-commands-remote-prefix
Prune remote tracking branches:
# Remove stale remote tracking branches
git fetch --prune origin
List stale local branches:
# Show branches not updated in 30+ days
git for-each-ref --sort=-committerdate refs/heads/ --format='%(refname:short) | %(committerdate:relative)' | grep -E 'weeks|months|years' ago
Offer to delete stale branches (interactive)
4. Smart Change Detection
Detect what changed to determine necessary steps:
# Check if package.json changed
DEPS_CHANGED=$(git diff HEAD@{1} HEAD -- package.json yarn.lock)
# Check if prisma schema changed
SCHEMA_CHANGED=$(git diff HEAD@{1} HEAD -- prisma/schema.prisma prisma/migrations/)
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 · 378 lines · 7 tokens per session scan C 54fb14e60291
local-sync is a command published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 2,117 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). It is 89% identical to local-sync, differing in 22 lines, and is treated as a copy.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.