~ / rigs / finolabs / vibecode

finolabs/vibecode

One engineering practice for AI coding agents: routing, delegation, review gates and verification for Claude Code, Codex and Antigravity.

↗ GitHub ★ 4 MIT updated 1d ago project Claude CodeCodex Claude plugin
stack: Python
share on X
ARCHETYPE
Skill Collector
Ten-plus skills loaded on demand. A procedural-knowledge library.
CONTEXT TAX · EVERY TURN
~9.1k tokens
Heavy · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details
Quality 5/100 Guardrails v2

Copy this rig

# review before running: this installs third-party code
$ npx degit finolabs/vibecode/agents ./rig-vibecode/agents
$ npx degit finolabs/vibecode/skills ./rig-vibecode/skills

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ npx degit finolabs/vibecode/skills/advisor .claude/skills/advisor
$ npx degit finolabs/vibecode/skills/afk .claude/skills/afk
$ npx degit finolabs/vibecode/skills/ask .claude/skills/ask
$ npx degit finolabs/vibecode/skills/brb .claude/skills/brb
$ npx degit finolabs/vibecode/skills/checks .claude/skills/checks
$ npx degit finolabs/vibecode/skills/coding-router .claude/skills/coding-router
$ npx degit finolabs/vibecode/skills/commit-messages .claude/skills/commit-messages
$ npx degit finolabs/vibecode/skills/delegate .claude/skills/delegate
$ npx degit finolabs/vibecode/skills/gtg .claude/skills/gtg
$ npx degit finolabs/vibecode/skills/handoff .claude/skills/handoff
$ npx degit finolabs/vibecode/skills/help .claude/skills/help
$ npx degit finolabs/vibecode/skills/open-source-review .claude/skills/open-source-review
$ npx degit finolabs/vibecode/skills/pause .claude/skills/pause
$ npx degit finolabs/vibecode/skills/plugin-packaging .claude/skills/plugin-packaging
$ npx degit finolabs/vibecode/skills/restore-point .claude/skills/restore-point
$ npx degit finolabs/vibecode/skills/review-gate .claude/skills/review-gate
$ npx degit finolabs/vibecode/skills/security-review-gate .claude/skills/security-review-gate
$ npx degit finolabs/vibecode/skills/session-hygiene .claude/skills/session-hygiene
$ npx degit finolabs/vibecode/skills/setup .claude/skills/setup
$ npx degit finolabs/vibecode/skills/shape .claude/skills/shape
$ npx degit finolabs/vibecode/skills/status .claude/skills/status
$ npx degit finolabs/vibecode/skills/tidy .claude/skills/tidy
$ npx degit finolabs/vibecode/skills/update .claude/skills/update
$ npx degit finolabs/vibecode/skills/versioning .claude/skills/versioning
$ curl -fsSL --create-dirs -o .claude/agents/navigator.md https://raw.githubusercontent.com/finolabs/vibecode/main/agents/navigator.md
$ curl -fsSL --create-dirs -o .claude/agents/reviewer.md https://raw.githubusercontent.com/finolabs/vibecode/main/agents/reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/security-reviewer.md https://raw.githubusercontent.com/finolabs/vibecode/main/agents/security-reviewer.md

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 16.2k rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(./.env.*)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(git push --force:*)",
      "Read(**/*.pem)",
      "Read(.env)",
      "Read(~/.aws/**)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Bash(rm -rf *)",
      "Bash(sudo *)",
      "Bash(sudo:*)",
      "Bash(rm -rf /)",
      "Bash(git push -f:*)",
      "Read(.env.*)",
      "Bash(git reset --hard*)",
      "Bash(rm -rf /*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(gh pr merge *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(gh pr merge:*)",
      "Bash(gh pr create *)",
      "Bash(git reset --hard:*)",
      "Bash(npm publish:*)",
      "Bash(git rebase *)"
    ]
  }
}

Skills (24)

Subagents (3)

navigator
model: inherit
Checks whether a project or spec is on course, drifting or abandoned against confirmed anchors, with evidence and up to three steering options and their costs. Use when a user story closes, before a r
reviewer
model: inherit
Reviews a pull request or commit range for defects nobody has named yet (bugs, regressions, broken consumers, missing tests): the changed code first, then the callers, dependencies and contracts it af
security-reviewer
model: inherit
Security review of a pull request or commit range: the changed code first, then every trust path that reaches it, with a permission-boundary review where it crosses authentication, authorization, tena

Similar rigs

copied ✓