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 nortonx/ai-tooling-free --skill ship-itgit clone --depth 1 https://github.com/nortonx/ai-tooling-freeWrote 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/nortonx/ai-tooling-free/ship-it)<a href="https://agentmods.dev/skills/nortonx/ai-tooling-free/ship-it"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/ship-it/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/nortonx/ai-tooling-free/ship-it"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/ship-it.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.00062 | $0.00734 |
| Opus 5 | $0.00031 | $0.00367 |
| Sonnet 5 | $0.00012 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
ship-it 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship it
⚠️ Review the changes first. Show the working-tree status and the commit message you're about to use, and confirm the changes are what's intended — this stages everything, commits, and pushes to remote. Running
/ship-itis the user's explicit authorization to commit and push for this run (it waives the usual "ask before committing/pushing" rule for this invocation only).
Arguments
[branch-name-or-issue-id] — optional. Overrides the branch name only; the commit message is always auto-derived from the diff.
- A full branch name (
feat/checkout-retry) is used verbatim. - A bare issue/ticket id (
123) becomes<type>/<issue-id>-<slug>. - Omitted →
<type>/<slug>derived from the diff.
(Copilot CLI and skills don't substitute $ARGUMENTS — include the branch name or issue id inline in your prompt when you want to override.)
Steps
- Gather context — run:
Resolve the default branch:git branch --show-current git status --short git diff --stat HEAD git log --oneline -10git symbolic-ref --quiet --short refs/remotes/origin/HEAD(strip theorigin/prefix); fall back tomain, elsemaster. - If the working tree is clean, stop and say "nothing to ship". Do nothing else.
- Branch:
- On the default branch (
main/master) → create and switch to a new branch (git switch -c <name>). Name it from the argument if given, else derive<type>/<slug>—<type>∈feat|fix|refactor|docs|test|chore|perf|ci,<slug>= short kebab summary of the change. An issue-id argument like123→<type>/<issue-id>-<slug>. - On a feature branch already → reuse it; do not create another.
- On the default branch (
- Stage everything:
git add -A. - Commit following the
create-commit-messageconvention:<type>: <imperative summary, ≤72 chars>— reference the issue id from the branch name when present (e.g.(#123)suffix). Focus the summary on the why. One commit only; do not split. Single quotes only if quoting. - Push with upstream tracking:
git push -u origin HEAD. - Report in 2–3 lines: branch name, commit subject, and push result (include any PR-create hint git prints).
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 · 45 lines · 62 tokens per session scan A 87f55596540f
ship-it is a skill published in the GitHub repository nortonx/ai-tooling-free (1 stars, last pushed 26d ago), licensed MIT. It adds 62 tokens to every session and 734 once invoked, about $0.0003 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
git-workflow
Use this skill for anything related to Git and version control workflows. Trigger when the developer asks for help with commit messages, PR descriptions, pull request reviews, branching strategies, changelog generation, release notes, code review etiquette, or Git conventions. Keywords: commit, PR, pull request…
git-workflow-and-versioning
Best practices for git commits, versioning, branch management, and release tagging.
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
utility-pm-changelog-curator
Draft CHANGELOG entries from git log via the pm-changelog-curator sub-agent, applying the repo hygiene rules (describe what changed, public paths only, no attribution trailers). Returns a layered draft with a status summary for maintainer review; refuses a dirty working tree unless --committed-only is passed. Use when…
intuitive-squash
Squash local GSD or agent-generated commit history into a clean, reviewable story while preserving important fixes. Use when the user asks to squash commits, clean git history, compress phase commits, prepare a branch before PR, compare aggressive vs moderate squash options, or preserve hotfix/security commits during…
git-commit
Safely create a git commit by validating repository state, staging intended changes, scanning for secrets/conflicts, generating a Conventional Commits message (repository convention first, else an English Angular default) from the staged diff, and committing without amend.