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.
curl -O https://raw.githubusercontent.com/finos/git-proxy/main/.agents/skills/implement/SKILL.mdgit clone --depth 1 https://github.com/finos/git-proxyWrote 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.
[](https://agentmods.dev/skills/finos/git-proxy/implement)<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.
<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>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once 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 |
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.
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.
- 1mo ago First seen · 114 lines · 0 tokens per session scan A e501778a37cb
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.
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…
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…
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…
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.
switch-github-creds
A skill to switch GitHub credentials for the agent.
fluxcd
Operate Flux GitOps with GitRepository, Kustomization, and HelmRelease pipelines; trace Ready conditions, suspend for incidents, and debug reconcile stalls agents routinely miss.