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/smart-ai-memory/attune-ai/commit-push-prnpx skills add Smart-AI-Memory/attune-ai --skill commit-push-prgit clone --depth 1 https://github.com/Smart-AI-Memory/attune-aiWhat 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.00017 | $0.00259 |
| Opus 5 | $0.00009 | $0.00130 |
| Sonnet 5 | $0.00003 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
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 3d 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.
What it actually says
commit-push-pr
One-shot command to commit current work, push, and open a PR.
Context (pre-computed)
git status -u
git diff --stat
git log --oneline -5
git branch --show-current
Instructions
- Review the git status and diff above
- Stage all relevant changed files (exclude .env, credentials, large binaries)
- Write a conventional commit message based on the
changes:
feat:for new featuresfix:for bug fixesdocs:for documentationchore:for maintenancerefactor:for restructuring
- Commit with the message
- Push the current branch to origin (create remote
branch if needed with
-u) - Create a PR targeting main using
gh pr createwith a summary and test plan - Return the PR URL
If on main, create a feature branch first based on
the change type (e.g., feat/description or
fix/description).
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.
- 3d ago First seen · 40 lines · 17 tokens per session scan A a7defd8efe3c
commit-push-pr is a skill published in the GitHub repository Smart-AI-Memory/attune-ai (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 17 tokens to every session and 259 once invoked, about $0.0001 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
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
oma-scm
SCM (software configuration management) and Git: branching, merges, conflicts, worktrees, baselines, audit readiness, plus Conventional Commits and safe staging.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…
merge-worktree
Squash-merge the current worktree branch into the main branch (or a specified target). Analyzes git history and source code to craft a comprehensive commit message.
git-commit-conventions
Standardize Git branch, commit, PR, author, and push workflows. Use when Codex needs to create commits, rename or rewrite commit messages, normalize PR branch history, preserve a contributor identity, or push branches according to repository rules such as Conventional Commits.
conventional-commits
Enforces strict adherence to the Conventional Commits 1.0.0 specification for staging and saving changes. Use when a user asks to commit files, draft a git message, or finalize code tasks.