~ / rigs / Ido-Levi / Hephaestus

Ido-Levi/Hephaestus

Semi-Structured Agentic Framework. Workflows build themselves as agents discover what needs to be done, not what you predicted upfront.

↗ GitHub ★ 1,031 other updated 10mo ago project Claude CodeCodex
share on X
ARCHETYPE
Minimalist
Lean instructions, few tools, tiny context tax. Lets the model think.
CONTEXT TAX · EVERY TURN
~986 tokens
Featherweight · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details

Copy this rig

# review before running: this installs third-party code
$ npx degit Ido-Levi/Hephaestus/.claude ./rig-hephaestus  # inspect, then merge into .claude/

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/backend-completion-specialist.md https://raw.githubusercontent.com/Ido-Levi/Hephaestus/main/.claude/agents/backend-completion-specialist.md
$ curl -fsSL --create-dirs -o .claude/agents/docs-accuracy-auditor.md https://raw.githubusercontent.com/Ido-Levi/Hephaestus/main/.claude/agents/docs-accuracy-auditor.md
$ curl -fsSL --create-dirs -o .claude/agents/senior-react-developer.md https://raw.githubusercontent.com/Ido-Levi/Hephaestus/main/.claude/agents/senior-react-developer.md

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

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

Subagents (3)

backend-completion-specialist
model: sonnet
Use this agent when you need a comprehensive backend task completed from start to finish in a Python codebase. This includes implementation, testing, validation, and proper integration. Examples:\n\n<
docs-accuracy-auditor
model: sonnet
Use this agent when you need to verify and update documentation files in the docs/ folder to ensure they accurately reflect the current codebase implementation and are readable/understandable. This ag
senior-react-developer
model: sonnet
Use this agent when you need to implement frontend features, UI components, or pages in React. This agent excels at creating visually consistent, well-designed user interfaces that align with existing

Similar rigs

copied ✓