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/sync-linear.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/sync-linear)<a href="https://agentmods.dev/commands/bybren-llc/rendertrust/sync-linear"><img src="https://agentmods.dev/badge/commands/bybren-llc/rendertrust/sync-linear/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/sync-linear"><img src="https://agentmods.dev/badge/commands/bybren-llc/rendertrust/sync-linear.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.00923 |
| Opus 5.5 | $0.00003 | $0.00369 |
| Sonnet 5.5 | $0.00001 | $0.00185 |
| Haiku 4.5 | $0.00001 | $0.00092 |
Grade A, and why
sync-linear 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.
This is a copy
97% identical to sync-linear — 10 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synchronize current branch work with Linear ticket, ensuring ticket reflects actual progress.
Sync Workflow
1. Get Current Ticket
Extract WOR number from branch:
git branch --show-current | grep -oE 'REN-[0-9]+'
Fetch ticket details:
mcp__claude_ai_Linear__get_issue {REN-number}
2. Analyze Work Done
Check commits since dev:
git log origin/dev..HEAD --oneline
git diff origin/dev --stat
Analyze:
- Number of commits
- Files changed
- Lines added/removed
- Work scope
3. Determine Status
Based on work analysis:
If commits exist but incomplete:
- Status: "In Progress"
- Add progress comment
If work complete, no PR:
- Status: "Ready for Review" or keep "In Progress"
- Add completion comment
If PR created:
- Status: "In Review"
- Link PR in comment
If PR merged:
- Status: "Done" (often auto-synced by GitHub-Linear integration for tickets referenced in commit messages)
- Manually close any child stories not referenced in commits
- Add completion timestamp
If blocked:
- Status: "Blocked"
- Document blocker
4. Update Ticket Status
Use Linear MCP to update:
mcp__claude_ai_Linear__update_issue
Update fields:
- Status (based on analysis)
- Progress percentage (if tracked)
- Labels (add "in-progress", "blocked", etc.)
5. Add Progress Comment
Create detailed comment:
## Progress Update - {date}
### Work Completed
- {commit 1 summary}
- {commit 2 summary}
- {commit 3 summary}
### Files Modified
- {file list with line counts}
### Next Steps
1. {next task}
2. {next task}
### Blockers
- {blocker if any}
### Timeline
- Started: {date}
- Current: {percentage}% complete
- Est. completion: {date/unknown}
Add comment via:
mcp__claude_ai_Linear__create_comment
6. Link Related Items
If applicable:
- Link to PR (if created)
- Link to related tickets
- Link to documentation
- Reference design docs
7. Update Labels
Add appropriate labels:
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 · 206 lines · 7 tokens per session scan A daaa8faaaf11
sync-linear 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 923 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to sync-linear, differing in 10 lines, and is treated as a copy.
Other commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
standup
Review my git commits from the past workday and generate a standup summary.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.