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/sarutobisasuke8/agentops-template/handoffgit clone --depth 1 https://github.com/SarutobiSasuke8/agentops-templateWrote 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/sarutobisasuke8/agentops-template/handoff)<a href="https://agentmods.dev/commands/sarutobisasuke8/agentops-template/handoff"><img src="https://agentmods.dev/badge/commands/sarutobisasuke8/agentops-template/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 | $0.00010 | $0.00220 |
| Opus 5 | $0.00005 | $0.00110 |
| Sonnet 5 | $0.00002 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
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 4d 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
Produce a handoff in the AGENTS.md standard format for the work done in this session.
Steps:
-
Identify the changes from this session: read
git status,git diff, and consult the conversation history for what was actually done (not what was planned). -
Format the handoff exactly as:
## Change <one paragraph: what changed and why, in user-visible terms> ## Files - path/to/file.ext - path/to/other.ext ## Verification - <command run> — <result> - <UI/manual check performed> — <outcome> - <anything skipped, with reason> ## Risks / follow-ups - <residual risk or next action> -
Be concrete: name commands and outcomes, not "tested it works".
-
If a session log was created, link it under Files.
-
Do not invent verification — if it was skipped, say so.
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.
- 4d ago First seen · 31 lines · 10 tokens per session scan A d0ca1158d1d4
handoff is a command published in the GitHub repository SarutobiSasuke8/agentops-template (9 stars, last pushed 15d ago), licensed MIT. It adds 10 tokens to every session and 220 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
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
release
Walk the llmwiki release process step by step.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".
export-project
Export a single registered Gnosys project to a portable .json.gz bundle (round-trips with gnosys import project).