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/docs/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/docs)<a href="https://agentmods.dev/skills/finos/git-proxy/docs"><img src="https://agentmods.dev/badge/skills/finos/git-proxy/docs/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/docs"><img src="https://agentmods.dev/badge/skills/finos/git-proxy/docs.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.00014 | $0.00544 |
| Opus 5.5 | $0.00006 | $0.00218 |
| Sonnet 5.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 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
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.
- 1mo ago First seen · 48 lines · 14 tokens per session scan A 740594bcba14
docs is a skill published in the GitHub repository finos/git-proxy (262 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 544 once invoked, about $0.0001 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
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.