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 commands/bybren-llc/safe-agentic-workflow/end-workgit clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflowWrote 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/safe-agentic-workflow/end-work)<a href="https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/end-work"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/end-work.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 | $0.00006 | $0.00759 |
| Opus 5 | $0.00003 | $0.00380 |
| Sonnet 5 | $0.00001 | $0.00152 |
| Haiku 4.5 | $0.00001 | $0.00076 |
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 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 — 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 [{{TICKET_PREFIX}}-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.,
[{{TICKET_PREFIX}}-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__{{MCP_LINEAR_SERVER}}__update_issue
mcp__{{MCP_LINEAR_SERVER}}__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
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 · 166 lines · 6 tokens per session scan A f8a1d3143a94
end-work is a command published in the GitHub repository bybren-llc/safe-agentic-workflow (406 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 759 once invoked, about $0.0000 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 commands, from other repositories
plan
Hierarchical planning entry point — all 11 plan verbs in one command. v3.7.2 consolidates /aura-frog:plan- (10 commands) into a single dispatcher that routes via the plan-orchestrator skill. The legacy plan- aliases still work as thin stubs.
add-to-todos
Add todo item to TO-DOS.md with context from conversation.
dashboard
CLI status display — terse one-screen view of plan tree, active task, conflicts, freezes, token budget, recent decisions.
plan-freeze
Manually freeze a plan node, cascading to descendants. Alias for /aura-frog:plan freeze (v3.7.2+).
plan-next
Return and activate the next ready T4 task. Alias for /aura-frog:plan next (v3.7.2+).
plan-promote
Bubble a T4 discovery up to T2 or T1. Alias for /aura-frog:plan promote " " (v3.7.2+).