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/githubnpx skills add gebruder/wirken --skill githubgit 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.00009 | $0.00366 |
| Opus 5 | $0.00005 | $0.00183 |
| Sonnet 5 | $0.00002 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
github 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
GitHub
Use the gh CLI for GitHub operations. The user must be authenticated (gh auth login).
Common operations
- List repos:
gh repo list - View repo:
gh repo view owner/repo - List issues:
gh issue list -R owner/repo - Create issue:
gh issue create -R owner/repo --title "Title" --body "Body" - List PRs:
gh pr list -R owner/repo - View PR:
gh pr view 123 -R owner/repo - Create PR:
gh pr create --title "Title" --body "Body" - Check CI status:
gh run list -R owner/repo --limit 5 - View run logs:
gh run view <run-id> --log-failed - Star a repo:
gh repo star owner/repo - Clone:
gh repo clone owner/repo - Search code:
gh search code "pattern" -R owner/repo - Search issues:
gh search issues "query" -R owner/repo
Tips
- Use
--jsonflag for machine-readable output:gh issue list --json number,title,state - Use
--jqfor filtering:gh pr list --json title,url --jq '.[].url' - Most commands accept
-R owner/repoto target a specific repository
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 · 43 lines · 9 tokens per session scan A 9bd101a6605c
github is a skill published in the GitHub repository gebruder/wirken (169 stars, last pushed 2d ago), licensed MIT. It adds 9 tokens to every session and 366 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…