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 skills/florianbruniaux/ccboard/shipnpx skills add FlorianBruniaux/ccboard --skill shipgit clone --depth 1 https://github.com/FlorianBruniaux/ccboardWrote 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/florianbruniaux/ccboard/ship)<a href="https://agentmods.dev/skills/florianbruniaux/ccboard/ship"><img src="https://agentmods.dev/badge/skills/florianbruniaux/ccboard/ship.svg" alt="Measured on agentmods" 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.00000 | $0.00552 |
| Opus 5 | $0.00000 | $0.00276 |
| Sonnet 5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
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 6d 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
/ship - Build, Commit, Push & Version Bump
Automates the complete ship workflow for ccboard:
Workflow Steps
-
Build Verification
- Run
cargo build --allto ensure compilation succeeds - Run
cargo clippy --all-targetsto catch warnings - Run
cargo test --allto verify tests pass - If any step fails, stop and report errors
- Run
-
Stage Changes
- Run
git statusto show current state - Stage all changes with
git add -A - Show what will be committed with
git diff --cached --stat
- Run
-
Commit
- Write a conventional commit message based on the changes:
feat:for new featuresfix:for bug fixesrefactor:for refactoringdocs:for documentationchore:for maintenance
- Commit format:
<type>: <description> - Add Co-Authored-By: Claude Sonnet 4.5 [email protected]
- Write a conventional commit message based on the changes:
-
Version Bump (optional)
- Check if Cargo.toml version needs bumping
- If user confirms, update version in all workspace crates
- Amend the commit with version bump
-
Push
- Push to current branch with
git push - If branch has no upstream, use
git push -u origin <branch>
- Push to current branch with
-
Summary
- Report what was shipped:
- Commit hash
- Branch name
- Files changed
- Version (if bumped)
- Report what was shipped:
Usage
# Basic usage - ship current changes
/ship
# With version bump
/ship bump
# Dry run - show what would be done
/ship --dry-run
Safeguards
- Always run full build + test suite before committing
- Never force push
- Never skip hooks (no --no-verify)
- Show clear summary of what will be committed before proceeding
- Fail fast on any build/test error
Expected Outcome
All changes committed, tested, and pushed to remote with proper conventional commit message.
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.
- 6d ago First seen · 76 lines · 0 tokens per session scan A b7f988c26ea9
ship is a skill published in the GitHub repository FlorianBruniaux/ccboard (95 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 552 tokens. 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-30.
Other skills, from other repositories
gsd-surface
Toggle which skills are surfaced — apply a profile, list, or disable a cluster without reinstall.
gsd-capture
Capture ideas, tasks, notes, and seeds to their destination.
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
gsd-profile-user
Generate developer behavioral profile and create Claude-discoverable artifacts.
gsd-fast
Execute a trivial task inline — no subagents, no planning overhead.
gsd-ns-ideate
Route to the appropriate exploration / capture skill based on the user's intent. gsd-note, gsd-add-todo, gsd-add-backlog, and gsd-plant-seed were folded into gsd-capture (with --note, default, --backlog, --seed modes) by #2790. The capture target lists pending todos via --list.