Borrowing it
Nothing to install: this file belongs to dlupiak/claude-session-dashboard. 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/dlupiak/claude-session-dashboard/main/.claude/skills/ship/SKILL.mdgit clone --depth 1 https://github.com/dlupiak/claude-session-dashboardWrote 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/dlupiak/claude-session-dashboard/ship)<a href="https://agentmods.dev/skills/dlupiak/claude-session-dashboard/ship"><img src="https://agentmods.dev/badge/skills/dlupiak/claude-session-dashboard/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/dlupiak/claude-session-dashboard/ship"><img src="https://agentmods.dev/badge/skills/dlupiak/claude-session-dashboard/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.00940 |
| Opus 5.5 | $0.00011 | $0.00376 |
| Sonnet 5.5 | $0.00005 | $0.00188 |
| Haiku 4.5 | $0.00003 | $0.00094 |
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 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship
Finalize the current feature branch: commit, push, create a PR, wait for approval, check CI, and merge.
Step 1: Verify branch
Run git branch --show-current and confirm you are NOT on main or master. If you are, STOP and tell the user to check out a feature branch first.
git branch --show-current
If the branch is main or master, abort with:
"You are on
main. Please check out a feature branch before shipping."
Step 2: Check for changes
Run git status and git diff --stat to see what needs to be committed.
- If there are no staged or unstaged changes and no untracked files, skip to Step 4 (push).
- If there are changes, proceed to Step 3.
git status
git diff --stat
Step 3: Commit
- Run
git diff(staged + unstaged) to understand all changes. - Run
git log --oneline -5to match the repo's commit message style. - Stage relevant files (use specific file names, never
git add -A). Do NOT stage files that look like secrets (.env, credentials). - Write a concise commit message summarizing the changes.
- Commit using a HEREDOC:
git commit -m "$(cat <<'EOF'
feat: <description>
Co-Authored-By: Claude Opus 4.6 <[email protected]>
EOF
)"
Step 4: Push
Push the branch to origin. Use -u if this is the first push.
git push -u origin $(git branch --show-current)
Step 5: Create PR
Check if a PR already exists for this branch:
gh pr view --json number,title,url 2>&1
- If a PR already exists, skip to Step 6.
- If no PR exists, create one:
- Run
git log --oneline main..HEADto understand all commits on this branch. - Run
git diff main...HEAD --statfor a change summary. - Create the PR:
gh pr create --title "<short title>" --body "$(cat <<'EOF'
## Summary
<bullet points summarizing changes>
## Test plan
<checklist of testing steps>
Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
- Report the PR URL to the user.
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 · 138 lines · 27 tokens per session scan A 3c54ff2f5251
ship is a skill published in the GitHub repository dlupiak/claude-session-dashboard (76 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 940 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.
github-release-management
GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.
ci-cd-ops
CI/CD pipeline patterns with GitHub Actions, release automation, and testing strategies. Use for: github actions, workflow, CI, CD, pipeline, deploy, release, semantic release, changesets, goreleaser, matrix, cache, secrets, environment, artifact, reusable workflow, composite action.
push-preflight
Secret-scans the commits a git push would send (gitleaks + regex layer; never history), then checks clean tree, forbidden files and fast-forward, with size and open-issue advisories. Refuses on any secret hit, no bypass. Triggers on: push to origin, push to github, push to remote, git push, can we push, safe to push…
shared-tooling-git-hooks
Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8.
ship
Commit, push, create PR(s), and auto-finalize — full automation pipeline. Handles uncommitted changes and recently created PRs.