Memtrace Index
syncable-dev/memtrace-public
Index a source-code repo into the Memtrace knowledge graph and poll the job to completion.
Codebase'i knowledge graph olarak analiz et. An agent skill from vibeeval/vibecosystem.
$ npx skills add vibeeval/vibecosystem --skill code-knowledge-graph -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vibeeval/vibecosystem code-knowledge-graph --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/code-knowledge-graph .claude/skills/code-knowledge-graph && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "code-knowledge-graph" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/code-knowledge-graph into .claude/skills/code-knowledge-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-knowledge-graph", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vibeeval/vibecosystem/tree/main/skills/code-knowledge-graphType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vibeeval/vibecosystem --skill code-knowledge-graph -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vibeeval/vibecosystem code-knowledge-graph --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/code-knowledge-graph .agents/skills/code-knowledge-graph && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "code-knowledge-graph" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/code-knowledge-graph into .agents/skills/code-knowledge-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-knowledge-graph", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vibeeval/vibecosystem --skill code-knowledge-graph -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vibeeval/vibecosystem code-knowledge-graph --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/code-knowledge-graph .cursor/skills/code-knowledge-graph && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "code-knowledge-graph" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/code-knowledge-graph into .cursor/skills/code-knowledge-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-knowledge-graph", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vibeeval/vibecosystem.git --path skills/code-knowledge-graph--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vibeeval/vibecosystem --skill code-knowledge-graph -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vibeeval/vibecosystem code-knowledge-graph --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/code-knowledge-graph .gemini/skills/code-knowledge-graph && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "code-knowledge-graph" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/code-knowledge-graph into .gemini/skills/code-knowledge-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-knowledge-graph", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vibeeval/vibecosystem code-knowledge-graphInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vibeeval/vibecosystem --skill code-knowledge-graph -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/code-knowledge-graph .github/skills/code-knowledge-graph && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "code-knowledge-graph" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/code-knowledge-graph into .github/skills/code-knowledge-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-knowledge-graph", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vibeeval/vibecosystem --skill code-knowledge-graph -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vibeeval/vibecosystem code-knowledge-graph --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/code-knowledge-graph .opencode/skills/code-knowledge-graph && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "code-knowledge-graph" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/code-knowledge-graph into .opencode/skills/code-knowledge-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-knowledge-graph", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
code-knowledge-graphCodebase'i knowledge graph olarak analiz et. An agent skill from vibeeval/vibecosystem.
Code Knowledge Graph is an agent skill from vibeeval/vibecosystem. Codebase'i knowledge graph olarak analiz et. Dependency, call graph, hotspot analizi.
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Knowledge Management, covering Knowledge graphs and Codebase onboarding. It works with Model Context Protocol. The repository describes itself as: AI software team for Claude Code - 138 agents, 295 skills, 73 hooks. Self-learning, multi-agent swarm, autonomous skill evolution. The licence is MIT.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 3b763b1. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
BashReadGlobGrepFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Code Knowledge Graph loads about 2.7k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 690 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Bash, Read, Glob, GrepAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from vibeeval/vibecosystem at commit 3b763b1, republished under its MIT licence (© vibeeval). 690 words, ~2,700 tokens.
.claude/skills/code-knowledge-graph/SKILL.md (or your agent's skills folder).Codebase'i knowledge graph olarak modeller. Dosya, modul, fonksiyon ve class'lar node; import, call, inheritance ve composition iliskileri edge olur. Sonuc: Mermaid diagram + JSON graph data.
Kod text degil, graph'tir. Her dosya diger dosyalara baglidir. Bu baglantilari anlamadan:
Knowledge graph tum bu iliskileri gorsellestirir ve olculebilir yapar.
/code-knowledge-graph [hedef-dizin] [--focus module] [--depth N] [--format mermaid|json|both]# Tum codebase analizi
/code-knowledge-graph src/
# Belirli module odaklan
/code-knowledge-graph src/ --focus auth
# Sadece circular dependency kontrolu
/code-knowledge-graph src/ --focus circular
# Hotspot analizi
/code-knowledge-graph src/ --focus hotspots
# Orphan/dead code tespiti
/code-knowledge-graph src/ --focus orphans# Dosya agaci
tldr tree ${PATH:-src/} --ext .py
# Kod yapisi: fonksiyonlar, class'lar, export'lar
tldr structure ${PATH:-src/} --lang pythonHer dosya, class, fonksiyon ve export bir node olur.
# Dosyanin import'lari (outgoing edges)
tldr imports ${FILE}
# Modulu kim import ediyor? (incoming edges)
tldr importers ${MODULE} ${PATH:-src/}
# Cross-file call graph
tldr calls ${PATH:-src/}Her import ve fonksiyon cagrisi bir directed edge olur.
# Architectural layer analizi
tldr arch ${PATH:-src/}Node'lar 3 katmana ayrilir:
| Katman | Tanim | Ornekler |
|---|---|---|
| Entry | Disaridan cagirilan, ici cagirmayan | routes, cli, main, handlers |
| Middle | Hem cagrilan hem cagirir | services, business logic |
| Leaf | Cagirilan ama baskasini cagirmayan | utils, helpers, constants |
# Bu fonksiyona kim bagimli?
tldr impact ${FUNCTION} ${PATH:-src/} --depth 3
# Dead code: hicbir yerden cagrilmayan fonksiyonlar
tldr dead ${PATH:-src/}codebase-memory MCP kuruluysa, persistent graph sorgusu yap:
mcp: index_status -> Repo index durumu
mcp: index_repository -> Repo'yu indexle (yoksa)
mcp: query_graph -> Graph sorgusu (iliskiler)
mcp: search_graph -> Pattern arama
mcp: get_architecture -> Mimari genel bakis
mcp: trace_call_path -> Fonksiyonlar arasi cagri yoluMCP, session'lar arasi kalici graph verisi saglar. tldr ise anlik taze analiz verir. Ikisini birlikte kullan.
A dogrudan B'yi import ediyor:
A --import--> BA, B'yi import ediyor, B de C'yi import ediyor. A, C'ye transitif bagimli:
A --import--> B --import--> C
A ....transitif....> CTransitive dependency chain'i uzadikca risk artar. tldr impact ile transitif zincirleri gor.
| Metrik | Yuksek Degerin Anlami | Risk |
|---|---|---|
| Fan-In (in-degree) | Cok modul buna bagimli | Fragile - degisiklik cascade yapar |
| Fan-Out (out-degree) | Bu modul cok seye bagimli | Unstable - disaridan kirilabilir |
Hedef: Leaf node'larda yuksek fan-in (iyi - utility), entry node'larda yuksek fan-out (kotu - god module).
Circular dependency = A imports B, B imports A (dogrudan veya transitif).
ONCE: A <--> B (circular)
SONRA: A --> IB <-- B (interface ile decouple)Her iki modul de bir interface'e bagimli olur, birbirine degil.
ONCE: A --> B --> A (circular)
SONRA: A --> B, A <-- C (C yeni modul, B'nin A'ya ihtiyac duydugu kismi tasir)ONCE: A <--> B (ortak kod paylasiyor)
SONRA: A --> Shared <-- B (ortak kod ayri module)ONCE: A --> B --> A (geri cagri)
SONRA: A --> EventBus <-- B (event ile haberlesme)| Durum | Strateji |
|---|---|
| Type/interface paylasimi | Extract Interface |
| Fonksiyon geri cagrisi | Dependency Inversion |
| Ortak utility kodu | Extract Shared Module |
| Async bildirim ihtiyaci | Event-Based Decoupling |
Hotspot = Graph'ta en cok baglantisi olan node.
hotspot_score = (in_degree * 2) + out_degree + (change_frequency * 3)in_degree * 2: Bagimli modul sayisi (en onemli - cascade risk)out_degree: Bagimlilik sayisi (kirilganlik)change_frequency * 3: Git log'dan degisiklik sikligi (degisen hotspot = en tehlikeli)| Hotspot Tipi | Oncelik | Aksiyon |
|---|---|---|
| Yuksek in-degree + sik degisen | P0 CRITICAL | Hemen split et, test ekle |
| Yuksek in-degree + stabil | P2 MEDIUM | Test ekle, dikkatli degistir |
| Yuksek out-degree | P1 HIGH | Dependency'leri azalt, facade pattern |
| Yuksek her ikisi | P0 CRITICAL | God module - parcala |
# Git log'dan en cok degisen dosyalar
git log --format=format: --name-only --since="6 months ago" | sort | uniq -c | sort -rn | head -20Cok degisen + cok baglantili = en yuksek risk.
graph TD
subgraph Entry["Entry Layer (Red)"]
routes[routes.py]
cli[cli.py]
end
subgraph Middle["Middle Layer (Orange)"]
auth[auth_service.py]
user[user_service.py]
end
subgraph Leaf["Leaf Layer (Green)"]
utils[utils.py]
validators[validators.py]
end
routes --> auth
routes --> user
cli --> user
auth --> utils
auth --> validators
user --> utils
style routes fill:#e74c3c,color:#fff
style cli fill:#e74c3c,color:#fff
style auth fill:#f39c12,color:#fff
style user fill:#f39c12,color:#fff
style utils fill:#27ae60,color:#fff
style validators fill:#27ae60,color:#fffgraph LR
handle_request --> validate
handle_request --> authorize
authorize --> check_token
authorize --> check_role
validate --> sanitize
check_token --> decode_jwtgraph LR
A[module_a] -->|imports| B[module_b]
B -->|imports| C[module_c]
C -->|imports| A
style A fill:#e74c3c,color:#fff
style B fill:#e74c3c,color:#fff
style C fill:#e74c3c,color:#fff
linkStyle 0 stroke:#e74c3c,stroke-width:3px
linkStyle 1 stroke:#e74c3c,stroke-width:3px
linkStyle 2 stroke:#e74c3c,stroke-width:3pxgraph TD
A[utils.py<br/>in:12 out:1<br/>HOTSPOT]
B[service.py<br/>in:3 out:8]
C[routes.py<br/>in:0 out:5]
D[models.py<br/>in:6 out:2]
C --> B
C --> A
B --> A
B --> D
D --> A
style A fill:#e74c3c,stroke:#c0392b,stroke-width:4px,color:#fff
style D fill:#f39c12,stroke:#e67e22,stroke-width:2px,color:#fffKnowledge graph review'da su sorulari cevaplar:
Impact sorusu: "Bu degisiklik kac modulu etkiler?"
tldr impact changed_function src/ --depth 3Coupling sorusu: "Bu yeni import cycle yaratir mi?"
Cohesion sorusu: "Bu modul cok mu fazla is yapiyor?"
Dead code sorusu: "Bu fonksiyon gercekten kullaniliyor mu?"
tldr impact function_name src/Yeni developer'a codebase'i tanitmak icin:
Graph verisi mimari kararlari destekler:
| Karar | Graph Verisi |
|---|---|
| "Bu modulu bolmeli miyiz?" | In-degree + out-degree + LOC |
| "Microservice siniri nerede?" | Cluster analizi (yuksek ic baglantilar, dusuk dis baglantilar) |
| "Hangi modulu once refactor edelim?" | Hotspot score siralamasina bak |
| "Yeni feature nereye oturur?" | Mevcut layer'a ve dependency pattern'ine bak |
| "Bu dependency guvenli mi?" | Transitif dependency chain'ine bak |
| Komut | Kullanim | Cikti |
|---|---|---|
tldr tree [path] | Dosya agaci | JSON |
tldr structure [path] --lang X | Kod yapisi (codemaps) | JSON |
tldr calls [path] | Cross-file call graph | JSON |
tldr impact <func> [path] | Reverse call graph | JSON |
tldr dead [path] | Dead/orphan code | JSON |
tldr arch [path] | Layer detection | JSON |
tldr imports <file> | Dosyanin import'lari | JSON |
tldr importers <module> [path] | Modulu kim import ediyor | JSON |
{
"metadata": {
"project": "project-name",
"analyzed_at": "2026-03-26T10:00:00Z",
"total_nodes": 45,
"total_edges": 128,
"languages": ["python"]
},
"nodes": [
{
"id": "src/auth/service.py::AuthService",
"type": "class",
"file": "src/auth/service.py",
"layer": "middle",
"in_degree": 5,
"out_degree": 3,
"is_hotspot": true,
"is_orphan": false
}
],
"edges": [
{
"source": "src/routes.py::handle_login",
"target": "src/auth/service.py::AuthService.authenticate",
"type": "call"
}
],
"layers": {
"entry": [],
"middle": [],
"leaf": []
},
"circular_dependencies": [],
"hotspots": [],
"orphans": []
}| Arac | Ne Zaman |
|---|---|
graph-analyst agent | Tam graph analizi, otomatik rapor |
tldr arch | Hizli layer detection |
tldr calls | Hizli call graph |
codebase-memory MCP | Persistent graph, session arasi sorgulama |
/explore architecture | Genel mimari kesfetme |
architect agent | Graph verisiyle mimari karar |
janitor agent | Orphan/dead code temizligi |
© vibeeval, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/code-knowledge-graph of vibeeval/vibecosystem.
Open the folder on GitHubat commit 3b763b1
Code Knowledge Graph next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Code Knowledge Graph this skillvibeeval/vibecosystem | 531 | — | ~2.7k | Automated safety check: Notes | MIT | |
| Memtrace Indexsyncable-dev/memtrace-public | 486 | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Explore Codebase with Graphtirth8205/code-review-graph | 32k | 1 repos | ~335 | Automated safety check: Pass | MIT | |
| Forgetful Repo EncodingScottRBK/forgetful | 301 | — | ~1k | Automated safety check: Pass | MIT | |
| Compasscrabbuild/compass | 168 | — | ~5k | Automated safety check: Pass | Custom licence | |
| Codebase Domain Flow ExtractorEgonex-AI/Understand-Anything | 85k | 1 repos | ~2.4k | Automated safety check: Pass | MIT |
syncable-dev/memtrace-public
Index a source-code repo into the Memtrace knowledge graph and poll the job to completion.
tirth8205/code-review-graph
Navigates a codebase through the code-review-graph MCP tools: architecture overview, symbol search, caller and callee tracing, flows and oversized functions.
ScottRBK/forgetful
Encodes a repository into the Forgetful knowledge base as a project, entities, atomic memories and documents, so a second run updates instead of duplicating.
crabbuild/compass
A skill your agent uses for graph-first AI coding sessions and repository analysis: session initialization, architecture maps, dependency or call-graph tracing, symbol and repository search…
Egonex-AI/Understand-Anything
Extracts business domains, flows and process steps from a codebase and produces an interactive horizontal flow graph, reusing an existing knowledge graph when one exists.
yonatangross/orchestkit
Read-side memory operations on the knowledge graph: search past decisions and patterns, load session context, view decision timelines, render Mermaid graph visualizations.
vibeeval/vibecosystem
Framework for measuring and tracking agent response quality over time.
vibeeval/vibecosystem
Security-focused differential code review with blast radius analysis, risk-adaptive depth (DEEP/FOCUSED/SURGICAL), git history correlation, and structured finding format.
vibeeval/vibecosystem
A skill your agent uses when making any factual claim about the codebase — existence, absence, or behavior.
vibeeval/vibecosystem
Systematic false positive verification for security findings.
vibeeval/vibecosystem
n8n otomasyon workflow'lari. An agent skill from vibeeval/vibecosystem.
vibeeval/vibecosystem
A skill your agent uses when context compression is imminent, when resuming a session, or when preserving critical decisions across long tasks.
Works with
Categories
Codebase'i knowledge graph olarak analiz et. An agent skill from vibeeval/vibecosystem. Code Knowledge Graph is an agent skill from vibeeval/vibecosystem. Codebase'i knowledge graph olarak analiz et.
Code Knowledge Graph fits situations like: tasks that involve Knowledge graphs; tasks that involve Codebase onboarding.
Run `npx skills add vibeeval/vibecosystem --skill code-knowledge-graph -a claude-code`. Or copy the skill folder (skills/code-knowledge-graph in vibeeval/vibecosystem) into .claude/skills/code-knowledge-graph in your project. Claude Code loads it when a task matches its description.
Run `npx skills add vibeeval/vibecosystem --skill code-knowledge-graph -a codex`. Or copy the skill folder (skills/code-knowledge-graph in vibeeval/vibecosystem) into .agents/skills/code-knowledge-graph in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vibeeval/vibecosystem --skill code-knowledge-graph -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-knowledge-graph, .gemini/skills/code-knowledge-graph, .github/skills/code-knowledge-graph and .opencode/skills/code-knowledge-graph in your project.
Going by SKILL.md and its folder, Code Knowledge Graph needs the command-line tools its instructions call (git). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Bash, Read, Glob, Grep.
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Code Knowledge Graph is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Code Knowledge Graph: Memtrace Index (syncable-dev/memtrace-public, 486 stars), Explore Codebase with Graph (tirth8205/code-review-graph, 32k stars), Forgetful Repo Encoding (ScottRBK/forgetful, 301 stars) and Compass (crabbuild/compass, 168 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
vibeeval (a GitHub user) maintains it in vibeeval/vibecosystem, which has 531 GitHub stars. The repository holds 144 skills in this directory. The repository was last updated on August 8, 2026.
Source: vibeeval/vibecosystem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.