git-proxy: Skill for Claude Code

.agents/skills/implement/SKILL.md

implement is a skill for Claude Code from finos/git-proxy. It costs 0 tokens per session (1,379 once invoked), scanned A, original, Apache-2.0.

A skill that carries a GitHub issue through investigation, planning, implementation, and pull-request preparation. A GitHub issue is a tracked request describing a bug, feature, or piece of work.

In plain words
What is it for?
Use it to implement an issue identified by its number or full GitHub URL. It fetches the issue, prepares a plan, changes the code after approval, commits the work, and produces a pull-request summary.
Why use it?
It connects the issue’s discussion to the relevant code and keeps the implementation process organised. It also requires confirmation before coding and records changes incrementally.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions subagents; names the AskUserQuestion tool; installed under .agents/ (shared by several agents).

This is finos/git-proxy's own configuration. It tells Claude Code how to work on git-proxy itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything git-proxy configures →

Reuse

Borrowing it

Nothing to install: this file belongs to finos/git-proxy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/finos/git-proxy/main/.agents/skills/implement/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/finos/git-proxy

Made for: Claude Code.

Wrote 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.

agentmods badge for implement

README.md
[![agentmods](https://agentmods.dev/badge/skills/finos/git-proxy/implement/github.svg)](https://agentmods.dev/skills/finos/git-proxy/implement)
Your own site
<a href="https://agentmods.dev/skills/finos/git-proxy/implement"><img src="https://agentmods.dev/badge/skills/finos/git-proxy/implement/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.

agentmods 80×15 button for implement

Your own site · 80×15
<a href="https://agentmods.dev/skills/finos/git-proxy/implement"><img src="https://agentmods.dev/badge/skills/finos/git-proxy/implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,379 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01379
Opus 5.5 $0.00000 $0.00552
Sonnet 5.5 $0.00000 $0.00276
Haiku 4.5 $0.00000 $0.00138

Measured 1mo ago against content hash e501778a37cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

.agents/skills/implement/SKILL.md · 114 lines

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

  1. 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 .nameWithOwner to get it).
  2. Fetch issue details:
    gh issue view <number> --repo <owner/repo> --json title,body,labels,assignees,comments
    
  3. 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
  4. 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

  1. List all configured remotes: git remote -v
  2. 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.
  3. Fetch and update main from the chosen remote:
    git fetch <remote>
    git checkout main
    git pull <remote> main
    
  4. 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 to feat/).
    git checkout -b <type>/<short-slug>
    
  5. Confirm to the programmer: "Created branch <branch-name> from <remote>/main."

Read the full file on GitHub · 114 lines

Changes

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.

  1. 1mo ago First seen · 114 lines · 0 tokens per session scan A e501778a37cb

Subscribe to this mod's changes

implement is a skill published in the GitHub repository finos/git-proxy (262 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,379 tokens. 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.

Related

Other skills, from other repositories

flux-controller-minor-releases

Run the upstream Flux controller minor release procedure for helm-controller, image-automation-controller, image-reflector-controller, kustomize-controller, notification-controller, source-controller, and source-watcher. Use when cutting a new controller minor release (vX.Y.0): creating the release series branch…

fluxcd/agent-skills · 89 tokens

flux-controller-patch-releases

Run the upstream Flux controller patch release procedure for helm-controller, image-automation-controller, image-reflector-controller, kustomize-controller, notification-controller, source-controller, and source-watcher. Use when preparing a new controller patch release from a release series branch, drafting changelog…

fluxcd/agent-skills · 80 tokens

commit-assisted-by

Add an Assisted-by: / git trailer to commits made during an AI-assisted coding session. Trigger on any git commit activity visible in the session — either commits you make yourself, or commits the user makes outside your tool calls that surface in the conversation — even without an explicit request. Also trigger when…

fluxcd/agent-skills · 98 tokens

argocd-expert

Expert-level ArgoCD GitOps deployment, application management, sync strategies, and production operations. Use when the user mentions GitOps, Kubernetes, continuous deployment, declarative, or automation, or when the task involves ArgoCD Architecture, Application CRD, AppProject, or ApplicationSet.

personamanagmentlayer/pcl · 65 tokens

switch-github-creds

A skill to switch GitHub credentials for the agent.

BrianV1981/aim · 17 tokens

fluxcd

Operate Flux GitOps with GitRepository, Kustomization, and HelmRelease pipelines; trace Ready conditions, suspend for incidents, and debug reconcile stalls agents routinely miss.

alivirgo/Major-AI-Skills · 36 tokens