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/deliver/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/deliver)<a href="https://agentmods.dev/skills/frostney/gocciascript/deliver"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/deliver/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/deliver"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/deliver.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.00049 | $0.02264 |
| Opus 5.5 | $0.00020 | $0.00906 |
| Sonnet 5.5 | $0.00010 | $0.00453 |
| Haiku 4.5 | $0.00005 | $0.00226 |
Grade A, and why
deliver 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deliver
Own one work item's outcome through its selected endpoint. Enter from its actual state, reuse settled decisions and valid evidence, and keep the parent task active when a child skill returns a fixable failure or pending transition.
Resolve scope and endpoint
Infer the repository and work item from the request, issue, bug description,
confirmed idea, current branch or PR. Verify identities and existing work before
mutation. Use /create-issue only when tracking is requested or required; an
unfiled idea can go directly to /implement.
The endpoint comes from the delivery settings. deployed
means the project's configured default integration destination, which may be
production, staging, nightly or another established target. Read project
instructions, delivery documentation and actual workflows to identify it; do not
assume production or choose among ambiguous destinations.
A delivery request authorizes the in-scope development, validation, publication,
feedback handling and Git operations needed for its endpoint, including merge
and the configured integration path for deployed. Preserve explicit limits,
repository protections and existing authorization. An earlier endpoint does not
authorize later operations. Complete independent work before asking for a
specific unresolved destination, provider, new infrastructure, spending or other
material
choice. Repair an existing integration workflow when an established
in-scope defect blocks delivery; do not replace its provider or invent a new
service as an incidental fix.
Delivery settings
Run node scripts/delivery-settings.mjs <project root>; the path is relative to
this skill directory. It reads the frontmatter of ORCHESTRATION.md beside
AGENTS.md and prints:
endpoint:ready-to-merge,mergedordeployed, defaultready-to-merge;entry-points:deliverorstop, defaultdeliver.
What ships with it
2 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 · +45 lines 17e28311c2fb
- 3d ago Changed · +3 lines 38d158303a2b
- 11d ago Changed · +12 lines 6e1de20a4109
- 18d ago Changed · +5 lines d1ea17ac52d5
- 22d ago Changed · +3 lines 9e1c737f5675
- 24d ago Changed · +6 lines 28f85f962f2c
- 26d ago Changed · +1 lines · +17 tokens per session f3c3a88a398a
- 29d ago First seen · 107 lines · 32 tokens per session scan A 89ae6779217e
deliver is a skill published in the GitHub repository frostney/GocciaScript (20 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 2,264 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
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
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…
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
operating-github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.