Brain Bed
Repository: brain-bed
Author: bbangjooo · Source status: Clear source
Forced meditation breaks for AI-fried brains.
Score basis:Clear source · Low risk signals · Universal
Compare skills
Pick 2–4 skills and compare what really matters: fit, risk, install effort, and community signal.
Comparison matrix
Highlights show current best; tooltip explains diff/best rules.
SAS-v2.1 diff rules / risk tag notes
Start with the matrix. Open this section when you need to understand audit grades, top threats, control gaps, and best-value highlights.
Suggested baseline
Search to add skills, or paste 2–4 comma-separated slugs.
How differences are detected
A row is marked different when selected skills have distinct values. Only-differences mode hides rows that are identical.
How best values are highlighted
Audit score, evidence confidence, trust score, and community signal prefer higher values; execution risk and install friction prefer lower values.
How to read risk tags
Risk tags come from SAS-v2.1 public-evidence signals and point to command, network, secret, context, or supply-chain items to review before install.
Selected audit signals
codex-oss-maintainer-toolkit
Execution risk:High
Threat tags:unexpected code execution, data exfiltration, human approval gap
Control gaps:missing license, broad permissions, shell without guardrails
ccNexus
Execution risk:High
Threat tags:unexpected code execution, data exfiltration, human approval gap
Control gaps:missing license, broad permissions, shell without guardrails
mcp-for-beginners
Execution risk:High
Threat tags:unexpected code execution, data exfiltration, memory context poisoning
Control gaps:missing license, broad permissions, shell without guardrails
| Dimension | codex-oss-maintainer-toolkit | ccNexus | mcp-for-beginners |
|---|---|---|---|
| SAS-v2.1 pre-install audit | |||
Threat tags | unexpected code execution, data exfiltration, human approval gap | unexpected code execution, data exfiltration, human approval gap | unexpected code execution, data exfiltration, memory context poisoning |
Evidence confidence | 65% | 65% | 67% |
| Source & provenance | |||
Provenance | IndianOldTurtledove/codex-oss-maintainer-toolkit | lich0821/ccNexus | microsoft/mcp-for-beginners |
Freshness | 2026-03-13 | 2026-03-23 | 2026-04-08 |
| Risk & trust | |||
Trust score | 74 | 82 | 85 |
| Community | |||
Stars | 45 | 816 | 15.8K |
Repository: rox
Author: BeWelcome · Source status: Clear source
:earth_africa: BeWelcome lets you share a place to stay, connect with travellers, meet up and find accommodation on your journey.
Score basis:Clear source · Low risk signals · Universal
Repository: splitrail
Author: Piebald-AI · Source status: Clear source
Fast, cross-platform, real-time token usage tracker and cost monitor for Gemini CLI / Claude Code / Codex CLI / Qwen Code / Cline / Roo Code / Kilo Code / GitHub Copilot / OpenCode / Pi Agent / Piebald.
Score basis:Clear source · Risk needs review · Universal
Repository: cc-statistics
Author: androidZzT · Source status: Clear source
AI Coding stats dashboard — track costs, tokens, and efficiency across Claude Code / Gemini CLI / Codex / Cursor Topics: ai-coding, claude-code, cli, cost-estimation, developer-tools, gemini-cli, macos-app, python, swift
Score basis:Clear source · Risk needs review · Universal