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 OutlineDriven/odin-claude-plugin --skill commit-push-prgit clone --depth 1 https://github.com/OutlineDriven/odin-claude-pluginWrote 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/outlinedriven/odin-claude-plugin/commit-push-pr)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/commit-push-pr"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/commit-push-pr/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/outlinedriven/odin-claude-plugin/commit-push-pr"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/commit-push-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 15 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Excessive Agency · line 42 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00046 | $0.03925 |
| Opus 5.5 | $0.00018 | $0.01570 |
| Sonnet 5.5 | $0.00009 | $0.00785 |
| Haiku 4.5 | $0.00005 | $0.00392 |
Grade A, and why
commit-push-pr 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit, push, and optionally open a pull request
Commit the working tree and push the feature branch to origin. In pull-request mode, open or update the pull request with gh; in no-PR mode, stop after the push. Commit authoring belongs to commit. Title and body authoring belongs to create-pull-request. This skill adds branch placement, the PR target resolution when a PR is requested, the push, and the gh call when a PR is requested.
Contract
| Field | Bound contract |
|---|---|
| Trigger | User asks to commit and push a feature branch, either with a pull request or without one. |
| Authority | Human-gated: both modes write local commits, at most one local feature branch, and one push to origin/<branch>. Pull-request mode also creates or edits one pull request through gh; no-PR mode creates no pull request. The skill states the mutation set before each remote mutation. Rollback is git reset --hard <prior-HEAD> for new commits, git branch -D <branch> for a branch this skill created, and, in pull-request mode, gh pr close or gh pr edit restoring the prior body for the PR. No remote mutation without the gate. |
| Side effect | Local commits, at most one local feature branch, and one git push to origin. Pull-request mode also creates or edits one PR on GitHub; no-PR mode does not create or edit a PR. No force push. |
| Done | No-PR mode: the branch is pushed with git status --porcelain empty and git rev-list --left-right --count origin/<branch>...HEAD printing 0 0. Pull-request mode: those checks pass and gh pr view --json url,title,state returns the PR as OPEN. |
Inputs
- Mode: optional; defaults to
pull-request. Usepull-requestto open or update a PR, orno-pull-requestto push the feature branch only. This selects whether PR-target resolution, title/body composition, and the PR call occur. - Working-tree state (
git status,git diff HEAD): required, gathered by the skill. - Current branch and recent history (
git branch --show-current,git log --oneline -10): required, gathered by the skill. - Remote default branch (
git rev-parse --abbrev-ref origin/HEAD, thengit ls-remote --symref origin HEAD, thengh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'verified againstgit ls-remote --heads origin <default>): required for branch placement in either mode. When every resolver fails, the skill stops; a default branch is never guessed. - Existing PR for the branch (
gh pr view --json url,title,state): required only in pull-request mode, gathered by the skill.NO_OPEN_PRwhen none exists. - Remotes (
git remote -v) and fork relationship (gh repo view <origin-slug> --json nameWithOwner,parent,defaultBranchRef): required for the PR target in pull-request mode; remotes are still gathered for the push in no-PR mode. ghinstalled and authenticated (gh auth status): required for pull-request mode. The default-branch fallback may still usegh repo viewin either mode.- Evidence supplied by the user (URL, image embed, artifact path): optional in pull-request mode, placed in the PR body as given.
- User decisions: detached HEAD, unpushed local default-branch commits, an ambiguous PR target, and whether to rewrite an existing PR's description.
What ships with it
1 file 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.
- 1mo ago Changed · +1 lines · -9 tokens per session bf8cae180387
- 1mo ago Changed · -83 lines · +24 tokens per session 75bade76766c
- 1mo ago First seen · 163 lines · 31 tokens per session scan A 624eef5ec1ab
commit-push-pr is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (37 stars, last pushed 21d ago), licensed Apache-2.0. It adds 46 tokens to every session and 3,925 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-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…