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/docsnpx skills add finos/git-proxy --skill docsgit 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.00014 | $0.00544 |
| Opus 5 | $0.00007 | $0.00272 |
| Sonnet 5 | $0.00003 | $0.00109 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
docs 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
Update existing project documentation to reflect the current state of the branch.
Read AGENTS.md first. It is the canonical project guide for this repository.
Steps:
- Run
git diff main...HEAD --statandgit log main..HEAD --onelineto understand what changed on this branch - Read the changed files to understand what was added, removed, or modified
- Read the current documentation files:
README.md,docs/Architecture.md,AGENTS.md,CLAUDE.md,.github/copilot-instructions.md - Identify documentation that is now outdated or missing based on the branch changes
- Apply minimal, targeted edits to bring docs in line with the code
What to update:
- Architecture.md — new push actions, configuration parameters, plugins, build steps, authentiction methods
- README.md — project description, features list, usage examples
- AGENTS.md — canonical project architecture, invariants, testing commands, and AI-agent workflow guidance
- CLAUDE.md — Claude-specific entry point that should remain aligned with
AGENTS.md - .github/copilot-instructions.md — short Copilot-compatible summary of the highest-priority repo rules
Principles:
- Minimal changes only. Do not rewrite sections that are already accurate. Edit the smallest possible region.
- Capture important information. New commands, config keys, classes, architecture changes, and breaking changes must be documented.
- Keep it concise. Prefer inline descriptions over new subsections. Use tables and bullet points. Avoid verbose prose.
- Match existing style. Follow the formatting, tone, and structure already in each file. Do not add headings, sections, or patterns that don't already exist.
- One edit per concern. If a section needs updating, make one focused edit rather than rewriting the whole section.
- Skip trivial changes. Internal refactors, renames, or implementation details that don't affect the public interface do not need doc updates.
After editing, report what was updated:
- List each file edited and a one-line description of the change
- If no docs needed updating, say "Documentation is up to date" and stop
Do NOT:
- Create new documentation files
- Add sections or headings that don't already exist
- Rewrite large blocks of text when a small edit suffices
- Document internal implementation details
- Add emojis, badges, or decorative elements
- Update docs for changes that don't affect user-facing behavior
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 · 48 lines · 14 tokens per session scan A 740594bcba14
docs is a skill published in the GitHub repository finos/git-proxy (243 stars, last pushed 2d ago), licensed Apache-2.0. It adds 14 tokens to every session and 544 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.