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/summary/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/summary)<a href="https://agentmods.dev/skills/finos/git-proxy/summary"><img src="https://agentmods.dev/badge/skills/finos/git-proxy/summary/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/summary"><img src="https://agentmods.dev/badge/skills/finos/git-proxy/summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 38 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00011 | $0.00563 |
| Opus 5.5 | $0.00004 | $0.00225 |
| Sonnet 5.5 | $0.00002 | $0.00113 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
summary 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.
What it actually says
Generate a concise implementation summary for a PR description.
Read AGENTS.md first. It is the canonical project guide for this repository.
Steps:
- First, run the
/docsskill to ensure documentation is up to date with the branch changes - Run
git diff main...HEAD --statandgit log main..HEAD --onelineto understand all changes on this branch - Read the changed files to understand what was implemented and why
- Get the current branch name:
git rev-parse --abbrev-ref HEAD - Write a summary suitable for a GitHub PR description
- Save the raw markdown summary (without the wrapping code fence) to
plans/<branch-name>-summary.md, replacing any/in the branch name with-
Summary format rules:
- The summary must be GitHub-flavored markdown that renders nicely in a PR description
- Do NOT use any headings (
#,##,###, etc.) — structure the summary with bold labels and line breaks instead - Use
**bold**for section labels (e.g.,**What:**,**Why:**,**Changes:**) - Use backtick-wrapped inline code for file names, config keys, commands, and identifiers
- Use markdown bullet points (
-) for listing changes - Use numbered lists for verification steps
- Use
[text](url)for hyperlinks when referencing issues or external resources - Start with
**What:**— a one-line statement explaining the change - Follow with
**Why:**— 2-3 sentences max explaining the motivation - Include
**Changes:**— key changes as bullet points (no nested bullets) - If there are new tests, add
**Tests:**with one line describing coverage - End with
**How to verify:**— concrete steps as a numbered list - Keep the total summary under 30 lines
- Do not repeat file paths or class names unnecessarily
- Focus on behavior changes, not implementation details
- Write in present tense, active voice
Output rules:
- Do NOT print the summary to the conversation
- Only save it to the file and tell the user where it was saved: "Summary saved to
plans/<branch-name>-summary.md"
Do NOT:
- Use headings (
#,##,###) anywhere in the summary - Use tables or badges
- List every single file changed
- Include generic boilerplate like "This PR adds..."
- Add emojis
- Over-explain things that are obvious from the diff
- Print the summary content in the conversation output
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 · 52 lines · 11 tokens per session scan A a277a986d8a2
summary is a skill published in the GitHub repository finos/git-proxy (262 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 563 once invoked, about $0.0000 per session on Opus 5.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.
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…
gitops-knowledge
Flux CD and Flux Operator expert — answers questions and generates schema-validated YAML for all Flux CRDs (not repo auditing or live cluster debugging). Use when users ask about Flux concepts, want manifests for HelmRelease, Kustomization, GitRepository, OCIRepository, ResourceSet, FluxInstance, or any Flux resource.…
gitops-repo-audit
Audit and validate Flux CD GitOps repositories by scanning local repo files (not live clusters) — runs Kubernetes schema validation, detects deprecated Flux APIs, reviews RBAC/multi-tenancy/secrets management, and produces a prioritized GitOps report. Use when users ask to audit, analyze, validate, review, or…
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…