Borrowing it
Nothing to install: this file belongs to ashishpatill/tell-proof. 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/ashishpatill/tell-proof/master/.cursor/skills/ship-loop/SKILL.mdgit clone --depth 1 https://github.com/ashishpatill/tell-proofWrote 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/ashishpatill/tell-proof/ship-loop)<a href="https://agentmods.dev/skills/ashishpatill/tell-proof/ship-loop"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/ship-loop/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/ashishpatill/tell-proof/ship-loop"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/ship-loop.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.00055 | $0.00623 |
| Opus 5.5 | $0.00022 | $0.00249 |
| Sonnet 5.5 | $0.00011 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
ship-loop 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 1mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship loop
Close the loop from “open PR” to “merged on the base branch.” No vibes. No attribution noise.
Invariants
- Semantic commits only —
feat|fix|docs|test|chore|refactor(scope): summary. One concern per commit. - No attribution — do not add
Co-authored-by,Signed-off-by, or names of tools/agents/people in commit subjects or bodies. - Push every cycle —
git push -u origin <branch>after each commit batch. - Do not force-push to a shared PR branch unless the user explicitly asks.
- Merge only when green — local gates pass (
pnpm test/ typecheck / package tests). Never wait on or re-run GitHub Actions; remote CI is out of scope unless the user explicitly asks about it. - Prefer the PR that contains the work just shipped — if multiple drafts stack, merge the tip that includes the rest (or merge base then tip in order).
Loop
| Step | Action |
|---|---|
| 1. Identify | gh pr view <n> / gh pr checks <n> — branch, base, checks, review threads |
| 2. Diagnose | Local typecheck/tests, Playwright eye for UI PRs, leftover draft status — not GitHub Actions |
| 3. Fix | Smallest change that clears a named local failure |
| 4. Commit | Semantic message, no attribution trailers |
| 5. Push | Upstream the branch |
| 6. Re-check | Re-run local gates; if red, go to 2 |
| 7. Ready | Undraft if still draft |
| 8. Merge | Only if user asked (merge / merge when ready). Prefer local green over remote CI. |
Local gates (Tell)
pnpm -F @tell/design-skills test # if engine touched
pnpm -F @tell/web typecheck
pnpm test # if broader
For showcase/UI: Playwright eye on /showcase — craft beat visible, no empty right gutter, no nav-only thumbs.
Stop conditions
- Done: PR merged, branch deleted optional, working tree clean vs base.
- Blocked: Missing permissions, failing required check you cannot fix, or user-required review — report the blocker; do not fake a merge.
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.
- 1mo ago First seen · 54 lines · 55 tokens per session scan A 18d7a723c407
ship-loop is a skill published in the GitHub repository ashishpatill/tell-proof (2 stars, last pushed 22d ago), licensed MIT. It adds 55 tokens to every session and 623 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-08-31.
Other skills, from other repositories
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.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
chained-pr
Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus.