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/issuenpx skills add finos/git-proxy --skill issuegit 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.00020 | $0.00474 |
| Opus 5 | $0.00010 | $0.00237 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
issue 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.
What it actually says
Create a GitHub issue markdown file from the details provided by the user.
Read AGENTS.md first. It is the canonical project guide for this repository.
The user will describe a bug, feature request, or discussion context (e.g. Slack conversations, error logs, reproduction steps). Your job is to turn that into a well-structured issue and save it to plans/.
Steps:
- Read the user's input to understand the problem, who reported it, and any logs or reproduction steps provided
- Investigate the codebase to identify relevant code paths, pinpoint where the issue likely originates, and gather context that would help a contributor understand the problem
- Write a concise GitHub issue markdown file and save it to
plans/issue-<short-slug>.md
Issue format:
- Start with
## <title>as the first line (this becomes the GitHub issue title) ### Problem— 2-3 sentences explaining the issue and its impact### Steps to Reproduce— numbered list (if applicable)### Expected Behavior— 1-2 sentences### Actual Behavior— include relevant log snippets in code blocks, keep them short (trim stack traces to the key lines)### Potential Root Cause— based on your codebase investigation, explain where the issue likely lives. Link to source code using upstream GitHub URLs:https://github.com/finos/git-proxy/blob/main/...#L<start>-L<end>.### Affected Files— table with file links and one-line role descriptions### Additional Context— bullet points for version info, related code paths, or anything else useful
Style rules:
- Keep it concise — the whole issue should be under 80 lines
- Use code blocks sparingly — only for key log lines and small code snippets
- Do not propose fixes or implementation approaches
- Do not add Labels, Description, or Title as separate sections — the
##heading is the title - Write for a contributor who knows the project but hasn't seen this specific bug
- No emojis
$ARGUMENTS
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 · 39 lines · 20 tokens per session scan A 72b2e1965c2b
issue is a skill published in the GitHub repository finos/git-proxy (243 stars, last pushed 2d ago), licensed Apache-2.0. It adds 20 tokens to every session and 474 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.