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/finos/git-proxy/commitnpx skills add finos/git-proxy --skill commitgit clone --depth 1 https://github.com/finos/git-proxyWhat 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.00014 | $0.00475 |
| Opus 5 | $0.00007 | $0.00237 |
| Sonnet 5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
commit 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 2d 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
Create a git commit for the current staged/unstaged changes using Conventional Commits.
Read AGENTS.md first. It is the canonical project guide for this repository.
Rules:
- Run
git statusandgit diffto understand what changed - Stage relevant files (prefer specific files over
git add -A) - Write a commit message following Conventional Commits format
- Use
--signoffto sign off using the committer's git config (do NOT hardcode any name/email) - Do NOT add Co-Authored-By or any other trailers beyond Signed-off-by
- If there are no changes, say so and stop
Commit format:
<type>[optional scope]: <description>
Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore
Scope (optional): a noun describing the affected area in parentheses. Common scopes: config, api, proxy, db, e2e, docker, ci.
Subject line rules:
- Imperative mood ("add", not "added" or "adds")
- Do NOT capitalize the first letter after the type prefix
- Do NOT end with a period
- Keep under 72 characters total
For breaking changes, add ! after the type/scope:
feat(config)!: rename queue config key
Examples of good messages:
- "feat(api): add support for rejection reason"
- "fix(config): handle invalid regex on commitConfig"
- "refactor(ts): remove any/as usages in push-actions"
- "test(proxy): add tests for Git hosts other than GitHub"
- "docs: update architecture diagram in Architecture.md"
- "build: bump express to 5.2.1"
- "chore: remove unused import in services/push.ts"
Commit command:
git commit --signoff -m "<type>[scope]: <description>"
Do NOT:
- Use long multi-line messages for simple changes
- Add Co-Authored-By trailers
- Use past tense ("added", "fixed")
- Hardcode any author name or email
- Omit the type prefix
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.
- 2d ago First seen · 66 lines · 14 tokens per session scan A 02d3e46d3d03
commit is a skill published in the GitHub repository finos/git-proxy (243 stars, last pushed 2d ago), licensed Apache-2.0. It adds 14 tokens to every session and 475 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-30.
Other skills, from other repositories
n8n-architect
Use when the user explicitly wants to create, edit, validate, sync, or troubleshoot n8n workflows, asks about n8n nodes or automation, or wants to use n8n-as-code in the current context root.
dependabot-batch
Use when reviewing Radar's weekly Dependabot PRs and replacing the safe, 72-hour-soaked updates with one changelog-vetted, tested PR.
test-radar
Use when building and testing Radar changes with the repository's real-instance smoke-test workflow.
visual-test
Use when visually testing Radar UI changes against a real Kubernetes cluster with Playwright screenshots.
qa-find-bugs
Drive the live product at https://dashboard.bex.co as a signed-in QA user (QAEMAIL / QAPASSWORD from .env), hunt real bugs across the hosting features, research each fix down to file:line, file the non-duplicate findings to the w6 board through /pm, and /ship the scheduled milestone. Use when the user asks to QA the…
pm
Inspect and maintain the repository's .pm workstreams, inbox notes, milestones, and tasks. Use when the user asks for PM board status or requests a supported board mutation such as creating, promoting, adding, or completing work.