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/summarynpx skills add finos/git-proxy --skill summarygit 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.00011 | $0.00563 |
| Opus 5 | $0.00005 | $0.00282 |
| Sonnet 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 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
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.
- 2d ago First seen · 52 lines · 11 tokens per session scan A a277a986d8a2
summary is a skill published in the GitHub repository finos/git-proxy (243 stars, last pushed 2d ago), licensed Apache-2.0. It adds 11 tokens to every session and 563 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.