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 EternallLight/tgc-skills --skill shipgit clone --depth 1 https://github.com/EternallLight/tgc-skillsWrote 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/eternalllight/tgc-skills/ship)<a href="https://agentmods.dev/skills/eternalllight/tgc-skills/ship"><img src="https://agentmods.dev/badge/skills/eternalllight/tgc-skills/ship/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/eternalllight/tgc-skills/ship"><img src="https://agentmods.dev/badge/skills/eternalllight/tgc-skills/ship.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.00769 |
| Opus 5 | $0.00024 | $0.00385 |
| Sonnet 5 | $0.00010 | $0.00154 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
ship 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 10d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship — polish → gate → push → PR → review loop
Runs the standard pre-merge pipeline on the current branch. It ends at a reviewed PR.
HARD RULE: this skill NEVER merges. Not on clean approval, not on green CI, not "to save a step". Merging is the human's move, always. The terminal state is a reviewed PR plus a report.
Arguments
- Optional PR title / extra instructions. If a PR already exists for the branch, reuse it.
Steps
- Preflight. Resolve the GitHub default branch, confirm the current branch is not
it, verify
git statusis coherent, and ensure the intended work is in the diff. - Polish. Run
tgc-skills:polishon the diff (correctness + simplification + over-engineering lenses; applies the safe findings). Skip only if the user says "no polish". - Gate. Run the repo's documented local or pre-push gate. Use hooks, project
instructions, and package scripts to discover reproducible commands. Do not claim
that copying GitHub Actions
run:lines reproduces actions, services, matrices, or external checks; when there is no local gate, say CI remains authoritative. - Commit. Follow the repo's commit convention, falling back to a conventional message. Stage only files belonging to the change; inspect the complete index before committing. Do not exclude intentional plans or documentation merely because of their names.
- Update the base if needed. Fetch the PR base/default branch. If the committed feature branch is behind, merge the fetched base, resolve conflicts explicitly, and rerun the local gate. Do not rebase a published branch or force-push.
- Push. Push normally, establishing an upstream if needed. Never force-push.
- PR. If none exists,
gh pr createwith a concise body: what changed, why, how it was verified. Note any DB migration prominently. - Review loop. Invoke
tgc-skills:review-loopon the PR; it reports its heartbeat path before dispatching the loop agent. - Report. PR URL, loop outcome (clean / max-iterations / non-converging), findings
fixed vs dismissed, gate evidence (what passed), and the current state of the hosted
checks (
gh pr checks). Only reach the ready-to-merge line once those checks are green or the user has explicitly authorised merging despite them; if any are still pending or failing, say so and stop short of the handoff instead. End with: "Ready for you to merge. Run/tgc-skills:mergedafter merging for the post-merge checks and cleanup."
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.
- 10d ago First seen · 58 lines · 49 tokens per session scan A ad4f43ee4152
ship is a skill published in the GitHub repository EternallLight/tgc-skills (8 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 769 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
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
github
Full GitHub CLI control — issues, PRs, code reviews, repo management. Uses gh CLI with auth detection, rate limiting, and templates. Triggers on: github, issue, pull request, PR, code review, repo, branch, label, assignee, milestone, release, workflow, actions.
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
release
Release gentle-pi through GitHub and npm. Trigger: release, publish, npm publish, GitHub release, version bump.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
parallel-pr-review
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.