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 TechNickAI/ai-coding-config --skill shipgit clone --depth 1 https://github.com/TechNickAI/ai-coding-configWrote 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/technickai/ai-coding-config/ship)<a href="https://agentmods.dev/skills/technickai/ai-coding-config/ship"><img src="https://agentmods.dev/badge/skills/technickai/ai-coding-config/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/technickai/ai-coding-config/ship"><img src="https://agentmods.dev/badge/skills/technickai/ai-coding-config/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.00039 | $0.01340 |
| Opus 5.5 | $0.00016 | $0.00536 |
| Sonnet 5.5 | $0.00008 | $0.00268 |
| Haiku 4.5 | $0.00004 | $0.00134 |
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 25d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship
Complete shipping workflow. When the user says "ship it", DO IT — don't ask for confirmation at every step. Only stop for: merge conflicts, test failures, ASK items from review, or errors.
Usage
/ship— Full workflow on current branch/ship --skip-tests— Skip test step (use when tests already passed)/ship --skip-review— Skip multi-review (use for trivial changes)/ship --quick— Skip both tests and review (docs-only, typo fixes)
Pre-flight
-
Branch check: If on main/master, STOP. Tell the user to create a feature branch first. Do not create branches for them — that's a decision about naming and scope.
-
Detect base branch: Check
git remote show originor common names (main, master, develop). This is the merge target. -
Check for uncommitted changes: If there are unstaged/staged changes, note what will be included. Stash them before merging if git would refuse the merge, then unstash after.
Step 1: Merge latest base branch
Use git rev-parse --abbrev-ref origin/HEAD (fast, local) to detect the base branch.
git fetch origin <base>
git merge origin/<base>
If merge conflicts occur, STOP and report them. Do not auto-resolve — merge conflicts require human judgment about which version is correct.
If already up-to-date, continue silently.
Step 2: Run tests
Detect the test runner from project context:
package.jsonscripts:test,test:unit,test:integrationpytest/python -m pytestgo test ./...cargo testmix testbundle exec rspec
Run the detected test command. If tests fail:
- Pre-existing failures (also fail on base branch): Note them, continue with a warning. These aren't your problem.
- New failures (pass on base, fail on branch): STOP. Report which tests broke. Do not ship broken code.
If no test runner is detected, skip with a note.
Skip this step if --skip-tests or --quick was passed.
Step 3: Multi-review with fix-first
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.
- 25d ago First seen · 184 lines · 39 tokens per session scan A b934b0479512
ship is a skill published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 25d ago), licensed MIT. It adds 39 tokens to every session and 1,340 once invoked, about $0.0002 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-22.
Other skills, from other repositories
dependabot
Comprehensive guide for configuring and managing GitHub Dependabot. Use this skill when users ask about creating or optimizing dependabot.yml files, managing Dependabot pull requests, configuring dependency update strategies, setting up grouped updates, monorepo patterns, multi-ecosystem groups, security update…
commit-message-storyteller
Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to "write a commit message", "generate a commit", "describe my changes", "what should I commit this as", "commit this"…
conventional-commit
Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.
git-commit
Generate intelligent, conventional commit messages based on staged changes. Analyzes diffs, categorizes changes, and creates meaningful commit messages. Use when ready to commit changes and want high-quality commit history.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
git-commit
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive…