~ / rigs / Fili999 / ai-hub

Fili999/ai-hub

One hub for your AI coding agents, skills and workflows: write them once, install them into Claude Code, Codex, Antigravity CLI and local models. Free, open source, runs on your computer.

↗ GitHub ★ 2 MIT updated 5d ago project Claude CodeCodexGemini CLI
share on X
ARCHETYPE
Minimalist
Lean instructions, few tools, tiny context tax. Lets the model think.
CONTEXT TAX · EVERY TURN
~903 tokens
Featherweight · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details
Quality 8/100 Guardrails v2

Copy this rig

# review before running: this installs third-party code
$ npx degit Fili999/ai-hub/agents ./rig-ai-hub/agents

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.

$ curl -fsSL --create-dirs -o .claude/agents/implementer.md https://raw.githubusercontent.com/Fili999/ai-hub/main/agents/own/implementer.md
$ curl -fsSL --create-dirs -o .claude/agents/planner.md https://raw.githubusercontent.com/Fili999/ai-hub/main/agents/own/planner.md
$ curl -fsSL --create-dirs -o .claude/agents/researcher.md https://raw.githubusercontent.com/Fili999/ai-hub/main/agents/own/researcher.md
$ curl -fsSL --create-dirs -o .claude/agents/reviewer.md https://raw.githubusercontent.com/Fili999/ai-hub/main/agents/own/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 *)"
    ]
  }
}

Subagents (4)

implementerMakes a focused change to code, documents or configuration following an agreed plan, with tests and a short report. Use it after the plan and acceptance criteria are clear, for work that should stay o
plannerTurns a vague or large request into a short plan with acceptance criteria, before any work starts. Use it at the start of any non-trivial job to clarify the goal, size and risk, and to decide whether
researcherFinds and checks information from reliable, dated sources and separates verified facts from assumptions. Use it for market or technical research, documentation lookups, comparing options, or any decis
reviewerChecks a result against its acceptance criteria with real evidence and gives a clear pass, fail or blocked, then an honest per-point critique. Use it before calling anything done, merging or publishin

Similar rigs

copied ✓