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/copeeetang/rednote-mind-skills/github-kbnpx skills add CopeeeTang/rednote-mind-skills --skill github-kbgit clone --depth 1 https://github.com/CopeeeTang/rednote-mind-skillsWhat 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.00123 | $0.01011 |
| Opus 5 | $0.00062 | $0.00505 |
| Sonnet 5 | $0.00025 | $0.00202 |
| Haiku 4.5 | $0.00012 | $0.00101 |
Grade A, and why
github-kb 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Knowledge Base
Unified skill for local repo management + social media hot topic tracking.
Configuration
KB_PATH: Default ~/github. Customize in project CLAUDE.md:
KB_PATH: /your/path
Commands
/github-kb search <keyword>
Search local knowledge base.
- Read
KB_PATH/CLAUDE.mdindex - Match keyword against names, descriptions, tags
- Display matches with paths
- Offer to explore repo details
/github-kb update
Sync index with filesystem.
- Scan KB_PATH for
.gitdirectories - Extract: name, README first line, tech stack tags
- Diff against existing CLAUDE.md
- Show changes, ask confirmation, write update
Index format (keep under 100 lines):
# GitHub Knowledge Base
| Name | Description | Path | Tags |
|------|-------------|------|------|
| repo | One-line desc | ./repo | tag1, tag2 |
/github-kb discover <topic>
Find trending repos from multiple sources.
-
Gather (parallel):
- Xiaohongshu: See references/xiaohongshu.md
- Twitter/X: See references/twitter.md
- Web:
mcp__tavily__tavily-searchquery"<topic> github"
-
Extract GitHub URLs from results
-
Enrich via
gh repo view owner/repo --json name,description,stargazerCount -
Present candidates with source attribution
-
Clone user-selected repos:
gh repo clone owner/repo -
Update index automatically
/github-kb xiaohongshu <keyword>
Direct Xiaohongshu search. See references/xiaohongshu.md.
/github-kb twitter <url>
Fetch Twitter/X content. See references/twitter.md.
Tools Reference
| Source | Tool/Method |
|---|---|
| Local repos | gh CLI, filesystem |
| Xiaohongshu | mcp__rednote__* tools |
| Twitter/X | Jina API via scripts/fetch_tweet.py |
| Web search | mcp__tavily__tavily-search |
AI-Driven Query (DeepWiki Mode)
When solving problems, proactively search the knowledge base:
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 131 lines · 123 tokens per session scan A d8415c138339
github-kb is a skill published in the GitHub repository CopeeeTang/rednote-mind-skills (20 stars, last pushed 6mo ago), licensed MIT. It adds 123 tokens to every session and 1,011 once invoked, about $0.0006 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
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…