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 skills add Deploy-Forward/convoy --skill convoy-endgit clone --depth 1 https://github.com/Deploy-Forward/convoyWrote 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/skills/deploy-forward/convoy/convoy-end)<a href="https://agentmods.dev/skills/deploy-forward/convoy/convoy-end"><img src="https://agentmods.dev/badge/skills/deploy-forward/convoy/convoy-end/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/skills/deploy-forward/convoy/convoy-end"><img src="https://agentmods.dev/badge/skills/deploy-forward/convoy/convoy-end.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.00053 | $0.00440 |
| Opus 5 | $0.00026 | $0.00220 |
| Sonnet 5 | $0.00011 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
convoy-end 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 12d 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
End a Convoy task
This skill is an explicit completion action. Never invoke it implicitly when the user merely says that a substep is done.
Run the portable CLI from the current worktree:
convoy end [--summary "one line"] [--push]
- Preserve
--pushonly when the user supplied it in this invocation. - Never add
--pushon the user's behalf and never turn an automatic heartbeat into push authorization. - Do not commit, stage, set an upstream, force-push, or select a different
remote.
convoy end --pushpermits exactly one plaingit pushafter the command verifies a clean attached branch with an existing upstream. - Treat
push_status: pushedas proof of push. A heartbeat row by itself is not proof that git changed remotely. - If identity is ambiguous, the worktree is dirty, HEAD is detached, or no upstream exists, report the refusal and leave git unchanged.
Codex's native invocation is $convoy-end --push; there is no supported
arbitrary /end extension point. Claude receives a project command at
.claude/commands/end.md, so /end --push is available there after the command is installed/reloaded.
The Codex and Claude Stop hooks use convoy end --hook. That automatic path
records a turn-end heartbeat only, emits no transcript or vendor identifiers,
and can never push.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 39 lines · 53 tokens per session scan A 653b144150d3
convoy-end is a skill published in the GitHub repository Deploy-Forward/convoy (0 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 440 once invoked, about $0.0003 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-09-05.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.