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 skills/tradebaas/groundwork/delivernpx skills add Tradebaas/Groundwork --skill delivergit clone --depth 1 https://github.com/Tradebaas/GroundworkWrote 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/tradebaas/groundwork/deliver)<a href="https://agentmods.dev/skills/tradebaas/groundwork/deliver"><img src="https://agentmods.dev/badge/skills/tradebaas/groundwork/deliver.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.00047 | $0.01075 |
| Opus 5 | $0.00023 | $0.00537 |
| Sonnet 5 | $0.00009 | $0.00215 |
| Haiku 4.5 | $0.00005 | $0.00108 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
deliver: shipping is a procedure, not an event
0. Entry conditions: all of them
verifypassed on everything in this release (evidence in STATE.md, not memory).code-reviewclean on everything in this release (blockers and majors resolved), or its trivial-tier skip recorded in STATE.md (verify§4 routes this).scope-guardclean; specs in this release at statusdone.- CI green on the exact commit being shipped. Local green is not CI green. No CI yet (no
remote/host)? Wire it now. First delivery is the moment. Genuinely impossible? Run the full
gate chain on a fresh clean checkout and record that explicit exception in STATE.md. On
GitHub, a first release also protects
main: the owner applies the runbookdocs/operations/branch-protection.mdwith repo admin. - On a platform stack (the stack file's header declares a hosted platform): the target instance and the repo still agree. Export the environment fresh and compare it against what is committed; whatever was changed directly in the platform editor since the last export is brought into the repo or deliberately dropped, and either way it happens before the release, not during it. A repo that is behind its own instance ships a release that overwrites work nobody reviewed. This is the platform's standard failure mode and the one CI cannot see: green on the commit says nothing about what the instance holds.
- The product holds persistent data →
docs/operations/backup-restore.mdexists and the restore has been performed once, for real. An untested restore is a hope, not a backup. - Compliance register (
docs/compliance/REGISTER.md) has no open blocking item. For a first release or new data/AI processing, runcomplyfirst. A first release also proves the rootSECURITY.mdholds: the reporting channel works (on GitHub: private vulnerability reporting enabled in the repo settings), and once the product is placed on the market its support period is published (complyfills the marked fields).
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.
- 3d ago First seen · 70 lines · 47 tokens per session scan A a2c9c7055373
deliver is a skill published in the GitHub repository Tradebaas/Groundwork (2 stars, last pushed 8d ago), licensed MIT. It adds 47 tokens to every session and 1,075 once invoked, about $0.0002 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 skills, from other repositories
publish-release
Publish the delivered batch as release notes, a PR to main, or a tagged release.
landed
Post-merge lifecycle. Verifies merge CI, optional deployment checks, cleans up branches, and prepares next phase.
release
Version release preparation workflow including changelog, version bump, and deployment checks. Triggers: REL, release, 發布, 版本發布, deploy, 部署, publish, 上線, ship, tag, 打標籤, 版本, version bump, 升版.
changelog-updater
Auto-update CHANGELOG.md following Keep a Changelog format. Triggers: CL, changelog, 變更, 版本, version, 更新日誌, whatsnew, release notes, 發布說明, 變更紀錄, history, 歷史, 更新紀錄, 新功能, new features, breaking changes.
git-doc-updater
Auto-check and update key documentation before Git commits to keep docs in sync with code. Triggers: docs, 文檔, 更新文檔, sync docs, release, 發布, documentation, 同步文件, 文件檢查, doc check, 發布前, before release, 準備發布.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.