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/cisco-open/ai-harness-toolkit/commit-and-push-changesnpx skills add cisco-open/ai-harness-toolkit --skill commit-and-push-changesgit clone --depth 1 https://github.com/cisco-open/ai-harness-toolkitWhat 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.00018 | $0.00830 |
| Opus 5 | $0.00009 | $0.00415 |
| Sonnet 5 | $0.00004 | $0.00166 |
| Haiku 4.5 | $0.00002 | $0.00083 |
Grade A, and why
commit-and-push-changes 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit and Push Changes
Commit all changes except specified files, with an auto-generated or user-provided commit message.
Instructions
Step 1: Show the current state of changes:
git status --short
Step 2: Identify files to exclude from the commit.
Always exclude:
- All files in
.cursor/folders - Files modified by external processes (not by us)
APM and OpenSpec deployed content:
Repos using APM or OpenSpec will have deployed content under .github/ (e.g., .github/skills/, .github/prompts/, .github/instructions/, .github/agents/, .github/hooks/) and possibly .claude/. These files should be committed so that every contributor and Copilot on github.com gets agent context without running apm install. Only apm_modules/ should be gitignored.
If apm install was run during this session and new deployed files appeared, include them in the commit. If deployed files appear in git status but were not expected, run apm install to verify they are in sync with apm.yml before committing.
To detect unintended modifications, compare the changed files against the conversation history. If a file appears in git status but was not edited during this session, treat it as potentially unintended. For APM/OpenSpec-managed repos, keep .github/ and .claude/ changes that come from apm install and only exclude .github/ files that are still unexpected after re-running apm install. For non-APM repos, exclude unexpected .github/ files that are clearly out of scope for this task.
Step 3: Stage only the files we intentionally modified:
git add <file1> <file2> ...
Do NOT use git add -A or git add . as this will stage unintended files.
Step 4: Generate the commit message.
- Extract the Jira key (try in order until one succeeds):
git branch --show-current | grep -oE '[A-Z]{2,}-[0-9]+'
git log --oneline -10 | grep -oE '[A-Z]{2,}-[0-9]+' | head -1
If no Jira key is found, ask the user for the story key. If the user confirms no Jira key is needed, proceed without one.
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 · 99 lines · 18 tokens per session scan A 4c61e6805532
commit-and-push-changes is a skill published in the GitHub repository cisco-open/ai-harness-toolkit (12 stars, last pushed 6d ago), licensed Apache-2.0. It adds 18 tokens to every session and 830 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…