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/end-work.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/end-work)<a href="https://agentmods.dev/commands/bybren-llc/rendertrust/end-work"><img src="https://agentmods.dev/badge/commands/bybren-llc/rendertrust/end-work/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/end-work"><img src="https://agentmods.dev/badge/commands/bybren-llc/rendertrust/end-work.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.00006 | $0.00749 |
| Opus 5.5 | $0.00002 | $0.00300 |
| Sonnet 5.5 | $0.00001 | $0.00150 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
end-work 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
95% identical to end-work — 8 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are completing a work session. Execute final checklist before context switch or session end.
Completion Checklist
1. Work Status
Verify current state:
git status
git log origin/dev..HEAD --oneline
Status options:
- Work Complete: Ready for PR
- Work In Progress: Safe stopping point, commit and document
- Blocked: Document blockers
2. Commit All Work
If uncommitted changes:
git add .
git commit -m "type(scope): description [REN-XXX]"
Verify all work committed:
git status # Should show clean working tree
3. Documentation Status
Quick check:
- Inline comments for complex logic?
- README updated if new feature?
- CLAUDE.md/CONTRIBUTING.md updated if workflow changed?
- Linear ticket status current?
4. Update Linear Ticket
Note: Tickets referenced in commit messages (e.g.,
[REN-XXX]) auto-sync to Done when the PR merges via the GitHub-Linear integration. Manually close any child stories not referenced in commits.
Based on work status:
If Complete:
- Update ticket status to "Ready for Review" or "In Progress"
- Add comment summarizing work done
- Link to PR if created
If In Progress:
- Update ticket with progress notes
- Document any blockers or questions
- Set status appropriately
If Blocked:
- Document blocker clearly
- Add comments to ticket
- Tag appropriate people
Use Linear MCP:
mcp__claude_ai_Linear__update_issue
mcp__claude_ai_Linear__create_comment
5. Context Preservation
If stopping mid-work, document:
- What was completed
- What's next
- Any decisions made
- Any blockers encountered
- Questions to discuss
Create context document if needed:
## Session Context - [Date]
### Completed
- Item 1
- Item 2
### Next Steps
1. Task 1
2. Task 2
### Decisions
- Decision 1: Rationale
### Blockers
- Blocker 1: Details
### Questions
- Question 1
6. Branch Status
Decide next action:
If Ready for PR:
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 · 166 lines · 6 tokens per session scan A 73ad8d64923d
end-work is a command published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 6 tokens to every session and 749 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to end-work, differing in 8 lines, and is treated as a copy.
Other commands, from other repositories
gsd:quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
standup
Review my git commits from the past workday and generate a standup summary.
gsd:remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
company-repo
Gestionar el repositorio Company Savia: crear, conectar, estado, sincronizar. El repositorio compartido de la empresa para conocimiento, mensajería y estado.
iterate
Execute a single Ralph loop iteration - complete one work unit from tasks.md with proper commits and progress tracking.
weekly-summary
Generate weekly work summary from git activity.