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/epam/ai-dial-chat/git-shipnpx skills add epam/ai-dial-chat --skill git-shipgit clone --depth 1 https://github.com/epam/ai-dial-chatWrote 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/epam/ai-dial-chat/git-ship)<a href="https://agentmods.dev/skills/epam/ai-dial-chat/git-ship"><img src="https://agentmods.dev/badge/skills/epam/ai-dial-chat/git-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 | $0.00122 | $0.01334 |
| Opus 5 | $0.00061 | $0.00667 |
| Sonnet 5 | $0.00024 | $0.00267 |
| Haiku 4.5 | $0.00012 | $0.00133 |
Grade A, and why
git-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 today.
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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Ship Skill
Full cycle for ai-dial-chat: checkout new branch from development → stage → commit
(Conventional Commits) → push → optional PR. Base branch is development.
Supporting files (read them when the step says so — don't inline everything up front):
.agents/skills/git-ship/areas.md— how to resolve the commitarea(scope) for this repo..agents/skills/git-ship/examples/commit-messages.md— type table, message + branch examples..agents/skills/git-ship/examples/pr-body.md— PR body template, rules, andgh pr createusage.
Step 0 — Detect mode (new branch vs. update existing)
git rev-parse --abbrev-ref HEAD # current branch
gh pr view --json number,url,state 2>/dev/null # open PR for current branch (if any)
- New-branch mode — current branch is
development(or another base branch), or there's no PR for it. Run the full cycle: Steps 1–6. - Update-existing mode — you're already on a feature branch and it has an open PR (or the
user says "push to the existing PR" / "update my PR"). Do not create a new branch and do
not run
gh pr create. Stay on the current branch, then:- Step 2 — review the changes.
- Step 4 — generate the commit message (reuse the existing PR's ticket; keep the same area/type).
- Step 5 — skip the
git checkoutlines; justgit add→git commit→git push. - Skip Step 6's
gh pr create. Pushing updates the open PR automatically. Only refresh the body (gh pr edit --body) if the user asks or the description is stale/missing. - Step 7 — report the existing PR link, not a new one.
Step 1 — Gather required context
- Ticket number — use the
ticketargument if passed. Else look in conversation context. If still not found, ask: "What is the ticket number?" - Area — if the
areaargument is passed, use it directly in Step 3. - Draft PR? — if the user said "draft", note it for Step 6.
This skill runs in a forked context (
context: fork), so it does not see the main conversation. Prefer passing arguments:/git-ship 7432 catalog.
What ships with it
3 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.
- today Changed · +1 lines d48f56be5b25
- 4d ago First seen · 134 lines · 122 tokens per session scan A 226cf2ab6923
git-ship is a skill published in the GitHub repository epam/ai-dial-chat (504 stars, last pushed today), licensed Apache-2.0. It adds 122 tokens to every session and 1,334 once invoked, about $0.0006 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-30.
Other skills, from other repositories
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…