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 aiatelie/ai-atelie --skill ship-taskgit clone --depth 1 https://github.com/aiatelie/ai-atelieWrote 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/aiatelie/ai-atelie/ship-task)<a href="https://agentmods.dev/skills/aiatelie/ai-atelie/ship-task"><img src="https://agentmods.dev/badge/skills/aiatelie/ai-atelie/ship-task/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/aiatelie/ai-atelie/ship-task"><img src="https://agentmods.dev/badge/skills/aiatelie/ai-atelie/ship-task.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.00046 | $0.02947 |
| Opus 5 | $0.00023 | $0.01473 |
| Sonnet 5 | $0.00009 | $0.00589 |
| Haiku 4.5 | $0.00005 | $0.00295 |
Grade A, and why
ship-task 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 9d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ship-task
A contributor workflow for AI Atelie. Orchestrates the full end-to-end loop a maintainer follows when shipping a task: understand → implement → verify in browser → blast-radius check → commit with semantic message → open PR with evidence.
This skill is dev-time only. It does not load into adapter sessions spawned by the editor.
When to invoke
- "Ship task / issue #N" — explicit ship request.
- "Implement and PR this" — when a code change must result in a PR, not just a diff.
- "Work on issue #N" when the user expects a finished, reviewable PR rather than a discussion.
Skip when:
- The user is exploring or debugging without a clear acceptance bar.
- The change is a one-line tweak the user wants reviewed verbally before committing.
- The user explicitly says "just edit, don't commit".
Hard preconditions (STOP if unmet)
This skill delegates to two other skills. Skills cannot programmatically invoke each other — Claude must coordinate. Before starting, verify both are loaded:
-
verify-with-playwrightis in the available skills list. -
semantic-commitis in the available skills list.
If either is missing, STOP and tell the user: "ship-task needs both verify-with-playwright and semantic-commit loaded. They live at .claude/skills/. Confirm they're present and retry."
Also verify:
-
ghCLI is authenticated (gh auth statussucceeds). -
bun run setup:attachhas been run on this machine at least once (Chromium profile at~/.local/state/aiatelie/chromium-profile/exists). Refresh every few weeks. No plaintext cookies/tokens are written anywhere — session data lives in Chromium's own binary store. - You're on a branch that isn't
main(or the user has explicitly OK'd shipping straight to main, which is unusual). -
bun run devis running on:5173(the verify step needs it).
The loop (paste this checklist into your reply and tick as you go)
- Step 1 — Understand the task (re-read issue, read related code, state acceptance criteria back).
- Step 2 — Implement (minimum change satisfying acceptance criteria; no drive-by refactors).
- Step 3 — Verify in browser (delegate to
verify-with-playwright). - Step 4 — Blast-radius regression check (write a named report, not a vibes summary).
- Step 5 — Commit with semantic message (delegate to
semantic-commit). - Step 6 — Open PR with evidence attached.
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.
- 9d ago First seen · 266 lines · 46 tokens per session scan A c8f341f07ff6
ship-task is a skill published in the GitHub repository aiatelie/ai-atelie (8 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 2,947 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
od-contribute
One-click contribution flow for OpenDesign (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship…
orbit-github
Open Orbit briefing skill — selected by the Orbit pipeline when GitHub is the user's only connected connector, or when the user explicitly scopes their daily digest to GitHub. Pulls the past 24 hours of PRs, review requests, issues, CI runs, and merges from the user's authenticated GitHub connection and renders them…
diff-review
Render the patch-edit run's accumulated changes as a reviewable diff, surface it through a GenUI choice surface, and persist the user's accept / reject decision into the artifact manifest.
od-plugin-contribute-open-design
Open a pull request adding a local OpenDesign plugin to the OpenDesign community catalog using gh CLI.
od-plugin-publish-github
Publish a local OpenDesign plugin to a new public GitHub repository using gh CLI.
git_commit_message
XR — the secure, self-hosted AI agent. BYOK · local-first · spend-capped · tamper-evident. by rrrtx.