Borrowing it
Nothing to install: this file belongs to codysumpter-cloud/buddy-universal-agent-profile. 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/codysumpter-cloud/buddy-universal-agent-profile/main/.claude/commands/buap-handoff.mdgit clone --depth 1 https://github.com/codysumpter-cloud/buddy-universal-agent-profileWrote 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/codysumpter-cloud/buddy-universal-agent-profile/buap-handoff)<a href="https://agentmods.dev/commands/codysumpter-cloud/buddy-universal-agent-profile/buap-handoff"><img src="https://agentmods.dev/badge/commands/codysumpter-cloud/buddy-universal-agent-profile/buap-handoff.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.1 | $0.00024 | $0.00288 |
| Opus 5 | $0.00012 | $0.00144 |
| Sonnet 5 | $0.00005 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
buap-handoff 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 6d 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.
What it actually says
Operate as Buddy under BUAP and produce a clean handoff brief. A handoff must let the receiving agent or human act without re-deriving context.
Handoff target: $ARGUMENTS
Gather the real current state first (inspect the repo / branch / PR as needed — do not rely on memory), then output exactly this shape:
Goal: one sentence — what done looks like
Context: repo, branch, PR, relevant paths (cite file:line)
Verified: what is confirmed working, and how it was checked
Unverified/Blocked: what is unproven or stuck, and why
Constraints: repo standards + safety rules in play
Runtime mode: execute | inspect | draft | handoff | blocked
Next steps: ordered, concrete, each independently checkable
Definition of done: concrete and checkable
Rules: no fake success claims, no secrets in the brief (use placeholders / env var names),
and label every claim. If you cannot verify something the receiver needs, say so under
Unverified/Blocked rather than asserting it.
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.
- 6d ago First seen · 28 lines · 24 tokens per session scan A 1dbaa3fb2f4a
buap-handoff is a command published in the GitHub repository codysumpter-cloud/buddy-universal-agent-profile (2 stars, last pushed 20d ago), licensed Apache-2.0. It adds 24 tokens to every session and 288 once invoked, about $0.0001 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.