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 RashadAnsari/myagents --skill commit-prgit clone --depth 1 https://github.com/RashadAnsari/myagentsWrote 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/rashadansari/myagents/commit-pr)<a href="https://agentmods.dev/skills/rashadansari/myagents/commit-pr"><img src="https://agentmods.dev/badge/skills/rashadansari/myagents/commit-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/rashadansari/myagents/commit-pr"><img src="https://agentmods.dev/badge/skills/rashadansari/myagents/commit-pr.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.00023 | $0.00767 |
| Opus 5.5 | $0.00009 | $0.00307 |
| Sonnet 5.5 | $0.00005 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
commit-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 yesterday.
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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
The ! prefix on each line below runs the shell command inline and injects its output before the prompt is submitted. If the lines below still show the literal commands, this platform does not expand them: run each command yourself first and use its output as the context.
- Current git status: !
git status - Current git diff (staged and unstaged changes): !
git diff HEAD - Current branch: !
git branch --show-current - Recent commits: !
git log --oneline -10 - Default branch: !
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name' 2>/dev/null || echo "main"
Your task
Based on the above changes, create a single git commit and create or update the pull request. Follow these steps in order:
Step 1: Branch check
Read the current branch from the context above.
If the current branch is main or master:
- Generate a short, kebab-case branch name that describes the staged changes (e.g.
fix-login-validation,add-user-settings). Keep it under 40 characters. - Run:
git checkout -b <branch-name>
Otherwise, stay on the current branch. Do not switch branches.
Step 2: Commit
Infer the commit message format from the recent commits shown above: match the exact style, prefix convention, casing, and structure used in this project. Do not impose an external convention if the project already has one.
Stage all changed files and create a single commit with the inferred message style.
Step 3: Push
Push the branch to origin:
git push -u origin <current-branch>
Step 4: Build PR title and body from branch diff
Run both in parallel:
git log <default-branch>..<branch> --oneline
git diff <default-branch>..<branch>
Using all commits and the full diff between the branch and the default branch:
- Derive a concise PR title that summarises the overall change (not just the latest commit).
- Derive a 2-4 sentence PR body that describes what the branch does as a whole.
Step 5: Create or update the PR
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.
- yesterday First seen · 88 lines · 23 tokens per session scan A 7d249030997c
commit-pr is a skill published in the GitHub repository RashadAnsari/myagents (6 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 767 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-10-15.
Other skills, from other repositories
git-ops
Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
papi-build
Invoke when executing a build via buildexecute. Covers branching, gestalt pre-build check, and post-build audit.
papi-auto
Continue an approved PAPI cycle through implementation, verification and review using bounded autonomy. Resume durable work without rebuilding it; propose new scope before persisting it.
code-commit
Commit code changes with well-structured messages following Conventional Commits. Use when ready to commit after implementation or bug fix.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.