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/katalalab/katala-os/github-author-contextnpx skills add katalalab/katala-os --skill github-author-contextgit clone --depth 1 https://github.com/katalalab/katala-osWhat 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.00047 | $0.00394 |
| Opus 5 | $0.00023 | $0.00197 |
| Sonnet 5 | $0.00009 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
github-author-context 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-author-context — GitHub contributor profile
Builds a factual profile from public GitHub data via gh CLI.
When to use
- "このリポの作者について調べて"
- "この PR の作者はどんな人？"
- "コントリビューターのバックグラウンドを調べて"
Do not use for:
- Internal/private user lookups (no access to private data)
- Anything that could constitute surveillance or PII extraction
Data sources
# Public profile
gh api users/<username>
# Recent repos
gh api users/<username>/repos --jq '[.[] | {name, language, stars: .stargazers_count, updated: .updated_at}] | sort_by(.updated) | reverse | .[0:10]'
# Recent public activity
gh api users/<username>/events/public --jq '[.[] | {type, repo: .repo.name, created: .created_at}] | .[0:20]'
# PRs to a specific repo
gh pr list --repo <owner>/<repo> --author <username> --state all --limit 20
Output format
## Author: <username>
- Name: ...
- Bio: ...
- Company: ...
- Location: ...
- Joined: ...
- Top languages: ...
- Notable repos: ...
- Activity pattern: ...
Hard-rule reminders
- Use only public GitHub API data.
- Do not include email addresses, personal details, or inferred PII in outputs.
- Frame analysis as observable patterns, not personal judgments.
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 · 55 lines · 47 tokens per session scan A 0e9c42555404
github-author-context is a skill published in the GitHub repository katalalab/katala-os (2 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 394 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…