Borrowing it
Nothing to install: this file belongs to frostney/GocciaScript. 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/frostney/GocciaScript/main/.agents/skills/delivery-wait/SKILL.mdgit clone --depth 1 https://github.com/frostney/GocciaScriptWrote 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/frostney/gocciascript/delivery-wait)<a href="https://agentmods.dev/skills/frostney/gocciascript/delivery-wait"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/delivery-wait/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/frostney/gocciascript/delivery-wait"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/delivery-wait.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.00039 | $0.02152 |
| Opus 5.5 | $0.00016 | $0.00861 |
| Sonnet 5.5 | $0.00008 | $0.00430 |
| Haiku 4.5 | $0.00004 | $0.00215 |
Grade A, and why
delivery-wait 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 yesterday.
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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delivery wait
Run scripts/delivery_wait.py whenever a workflow must await external GitHub
state. The harness passively waits for the command to finish; it must not
simulate waiting with model heartbeats.
Running a wait
Hosts limit how long one command may run, and a delivery transition can take longer. These rules keep a wait armed for as long as the transition needs:
- If the host can run a command in the background and resume the session when it exits, run the wait that way. Then end the turn, or continue only work independent of the awaited state. If that capability is absent, use the fallback below; never hold the turn open with a blocking wait.
- Set each invocation's
--deadlineinside the host's limit for one command, and keep the time the caller gives up on the transition separately. Atimed-outresult before that time means: run the wait again with the same--state. That resumes one wait; it is not a heartbeat. - Run the helper as the whole command, with nothing piped or chained after it, so the exit status the host reports is the helper's own. A host notice that the command finished says only that it ended; the result envelope says what happened.
- Keep one running wait per state file. Never detach a wait from the host, for
example with
setsid,nohupor&: a detached process cannot resume the session. - While a wait runs, do not inspect the state it covers. Act on its result.
The address-feedback CodeRabbit adapter's run follows the same rules. It
keeps no state file: run it again with the same arguments, and it re-reads the
head's state from GitHub.
Long commands and delegated lanes
Apply the same turn discipline to long builds, tests and other commands, in coordinators and workers alike. Start commands expected to outlast a short check through the host's tracked background execution. Keep the task or session ID, output location, exact revision, completion condition and resume action in the handoff. A launch acknowledgment is pending work, never passing evidence. Short commands and bounded diagnostic checks can stay in the foreground.
What ships with it
3 files 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.
- yesterday Changed · +51 lines 46970ec1987e
- 11d ago Changed · +27 lines cec7bf9c90a7
- 24d ago Changed · +20 lines e13df69bdef2
- 26d ago Changed · +11 lines 5e46acf04845
- 29d ago First seen · 58 lines · 39 tokens per session scan A 745e735878a3
delivery-wait is a skill published in the GitHub repository frostney/GocciaScript (20 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 2,152 once invoked, about $0.0002 per session on Opus 5.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-26.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.