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/gebruder/wirken/gitnpx skills add gebruder/wirken --skill gitgit clone --depth 1 https://github.com/gebruder/wirkenWhat 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.00006 | $0.00295 |
| Opus 5 | $0.00003 | $0.00148 |
| Sonnet 5 | $0.00001 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
git 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
Git
Perform git operations in the workspace.
Common operations
- Status:
git status - Log:
git log --oneline -20 - Diff:
git diff - Staged diff:
git diff --cached - Add files:
git add <file>orgit add -A - Commit:
git commit -m "message" - Branch:
git branch -a - Switch branch:
git checkout <branch>orgit switch <branch> - Create branch:
git checkout -b <branch> - Pull:
git pull - Push:
git push - Stash:
git stash/git stash pop - Blame:
git blame <file> - Search history:
git log --grep="pattern" - Find who changed a line:
git log -p -S "text" -- <file>
Tips
- Always check
git statusbefore committing - Use
git diff --statfor a summary of changes - Use
git log --oneline --graphfor branch visualization
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 · 45 lines · 6 tokens per session scan A 415b43c5c7ed
git is a skill published in the GitHub repository gebruder/wirken (169 stars, last pushed 3d ago), licensed MIT. It adds 6 tokens to every session and 295 once invoked, about $0.0000 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
defenseclaw-ops
Manage DefenseClaw enterprise security - scan components, manage tool permissions, view alerts, configure guardrails.
spec-writing
Spec-writing for Spec-Driven Development (SDD) skill for writing requirement specifications before implementation. Use when starting a new feature, planning work, writing requirements, or designing a component. Trigger keywords: spec, specification, SDD, plan feature, write requirements, design feature, spec-driven…
test-compliance-proxy
End-to-end smoke test for the Compliance Proxy. Use when the user wants to verify that the running compliance-proxy correctly MITM-intercepts HTTPS provider traffic on :3128, applies the compliance pipeline, and writes matching trafficevent rows (source = 'compliance-proxy') plus Prometheus counters. Trigger keywords…
frontend-arch-review
Audit the Control Plane UI + Agent Dashboard against the design-token / CSS framework architecture, including the Tailwind v4 + shadcn surface and the prime-shadcn-tokens.css @theme {} palette. Detects theme/mode-breaking offenders: hex / rgba / hsla literals in .module.css, hex / rgba inside style={{}} blocks in…
project-review
Run a full-system multi-role audit of the gateway using review prompts for 9 specialist roles — admin dashboard, client, API, architecture, security, compliance, and more. Findings from every role are remediated through the standard workflow. Trigger keywords: project review, multi-role review, full system audit…
gap-review
Review gaps between SDD documents (source of truth) and all related artifacts: architecture, requirements, OpenAPI specs, code implementation, and unit tests. Creates a plan and todo list to bring docs and code into alignment. Use when docs are out of sync with code, after code-heavy changes, or to audit spec-code…