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 rules/clezcoding/awesome-coolify/gsd-ship-labelsgit clone --depth 1 https://github.com/clezcoding/awesome-coolifyWhat 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.00397 | $0.00397 |
| Opus 5 | $0.00198 | $0.00198 |
| Sonnet 5 | $0.00079 | $0.00079 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
gsd-ship-labels 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 2d 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.
What it actually says
GSD Ship → Labels + Optional Changeset (mandatory)
When /gsd-ship (or any flow that runs gh pr create for a GSD phase) succeeds:
- Immediately run:
./scripts/gsd-ship-post.sh <pr-number>
This is non-optional. By default it:
- Applies ship labels via
scripts/gsd-pr-labels.sh --mode shipincludingautomerge - Clears
needs-changesetso Kodiak can merge phase PRs without a changeset - Strips Kodiak blockers (
status: needs-review, etc.) - Does not create a
.changeset/file (milestone-only npm release model)
For hotfix / out-of-band releases that need an immediate changeset:
./scripts/gsd-ship-post.sh <pr-number> --with-changeset
That opt-in path runs gsd-ensure-changeset.sh, commits + pushes the fragment, then applies ship labels.
Kodiak still only merges when required CI checks are green — automerge is the opt-in, not a force-merge.
Never push [ci skip] / [skip ci] onto a PR tip. Required checks (Lint, Test & Build, MegaLinter) are bound to HEAD; a skipped tip leaves them stuck at "Expected — Waiting for status to be reported" and Kodiak waits forever.
- Preview:
./scripts/gsd-ship-post.sh <n> --dry-run
If the Cursor afterShellExecution hook already ran gsd-ship-post, verify labels are present and skip a duplicate run.
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.
- 2d ago First seen · 40 lines · 397 tokens per session scan A cf713c83e99f
gsd-ship-labels is a cursor rule published in the GitHub repository clezcoding/awesome-coolify (0 stars, last pushed 4d ago), licensed MIT. It adds 397 tokens to every session, about $0.0020 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 cursor rules, from other repositories
cursorrules
When the user asks about changelog, use changelog-ai-mcp tools: parsechangelog, generateentry, bumpversion, compareversions.
release-management
Cursor rule "release-management" from floriscornel/todo-mcp, covering release management, version bumping, release process, pre-release checklist and automated publishing.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.