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/implementnpx skills add finos/git-proxy --skill implementgit 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.00028 | $0.01379 |
| Opus 5 | $0.00014 | $0.00690 |
| Sonnet 5 | $0.00006 | $0.00276 |
| Haiku 4.5 | $0.00003 | $0.00138 |
Grade A, and why
implement 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement a GitHub issue end-to-end: fetch the issue, plan, code with approval, commit incrementally, and generate a PR summary.
Read AGENTS.md first. It is the canonical project guide for this repository.
The argument is an issue number (e.g. /implement 42) or a full GitHub URL (e.g. /implement https://github.com/finos/git-proxy/issues/42). If no argument is given, ask the user.
Phase 1: Fetch issue
- Parse the argument:
- If it is a full URL like
https://github.com/{owner}/{repo}/issues/{number}, extract{owner}/{repo}and{number}. - If it is just a number, use the current repo (run
gh repo view --json nameWithOwner -q .nameWithOwnerto get it).
- If it is a full URL like
- Fetch issue details:
gh issue view <number> --repo <owner/repo> --json title,body,labels,assignees,comments - Display a summary to the programmer:
- Issue number and title
- Labels (if any)
- Body (truncated to ~40 lines if longer)
- Number of comments and any noteworthy discussion points
- Ask the programmer to confirm this is the right issue before proceeding. Use AskUserQuestion with options: "Proceed", "Show full issue body", "Cancel".
Phase 2: Branch setup
- List all configured remotes:
git remote -v - If there is more than one remote, ask the programmer which remote to use as upstream using AskUserQuestion (list the remote names as options). If there is only one remote, use it automatically.
- Fetch and update main from the chosen remote:
git fetch <remote> git checkout main git pull <remote> main - Create a new branch from main. The branch name must follow this convention:
- Format:
<type>/<short-slug>where<type>is a Conventional Commits type (feat,fix,refactor,docs,chore, etc.) and<short-slug>is a kebab-case summary derived from the issue title (3-5 words max). - Examples:
feat/dynamic-allocation-support,fix/event-watcher-reconnect,refactor/pod-spec-converter - Pick the type based on the issue labels and description (e.g. a bug report maps to
fix/, a feature request tofeat/).
git checkout -b <type>/<short-slug> - Format:
- Confirm to the programmer: "Created branch
<branch-name>from<remote>/main."
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 · 114 lines · 0 tokens per session scan A e501778a37cb
implement is a skill published in the GitHub repository finos/git-proxy (243 stars, last pushed 2d ago), licensed Apache-2.0. It adds 28 tokens to every session and 1,379 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.