Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add fivol/claude-make-better/plugin install featureWrote 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/fivol/claude-make-better/ship)<a href="https://agentmods.dev/skills/fivol/claude-make-better/ship"><img src="https://agentmods.dev/badge/skills/fivol/claude-make-better/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/fivol/claude-make-better/ship"><img src="https://agentmods.dev/badge/skills/fivol/claude-make-better/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.00131 | $0.03331 |
| Opus 5 | $0.00066 | $0.01665 |
| Sonnet 5 | $0.00026 | $0.00666 |
| Haiku 4.5 | $0.00013 | $0.00333 |
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 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship — land the change as a reviewed PR
simplify → review → commit → push → PR → report
Everything here is about delivery. Writing the code is the turn's ordinary work and needs no skill; this contract starts once the change is on disk.
The report is produced last, after the change is pushed and in the PR. Never lead with it.
Two ways this runs
Detect the mode once, at the start:
- Workspace context — you're inside a task worktree from the
workspaceskill: there is a<worktrees>/<task>/.feature.jsonfor the checkout you're in, and the workspace root has.claude/feature/config.json. Use each repo's configured base branch, span all involved repos, persist the dashboard artifacts, hand out pretty URLs. - Standalone — anything else (a plain repo/branch, invoked directly). Operate on the current git repo, PR into its default base branch, give how-to-verify instead of URLs. No worktree, no servers, no dashboard.
# ROOT = walk up from cwd to the dir holding .claude/feature/config.json; else the repo root
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/config.py" --root "$ROOT"
_override_applied: true and a .feature.json beside your checkout ⇒
workspace context. Otherwise standalone. The loader works in both — with no
config it just returns the shipped defaults.
Guard (standalone): never commit straight onto a base/default branch. If
git branch --show-current is the default branch, create a topic branch first
(git switch -c <kebab-topic>), then proceed. In workspace context the worktree
is already on its task branch — use it.
Policy comes from config, not from this file
Read it once per pass; every knob below ships with a default, so an unconfigured project behaves exactly as this file describes:
| Key | What it decides |
|---|---|
simplify |
{enabled, when} — whether step 1 runs, and after which changes |
code_review |
the gate in step 2: when it fires, how deep, what it may fix |
considerations |
the cross-cutting dimensions checked every pass (empty ⇒ step off) |
commit |
{per_pass, message_language} |
pr |
{enabled, draft, title_template, body_template} |
branch |
task-branch naming (prefix / template) |
output_language |
the language you write in |
report.chat_template |
the report's blocks — see step 5 |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 270 lines · 0 tokens per session scan A 483957efbb4b
ship is a skill published in the GitHub repository fivol/claude-make-better (5 stars, last pushed 28d ago), licensed MIT. It adds 131 tokens to every session and 3,331 once invoked, about $0.0007 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
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.
git-push
A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.