~ / rigs / yopazerbot / brieltje

yopazerbot/brieltje

Smetlede and Briel (Lede, Belgium) in 3D: a walkable village in the browser, alone or with up to 16 friends. Explore, Paintball, Action, and endless waves of Zombies. Three.js and Blender, made with Claude Code and OpenAI Codex..

↗ GitHub ★ 0 NOASSERTION updated 2d ago project Claude CodeCodexGemini CLI
share on X
ARCHETYPE
Pragmatist
A balanced, no-drama setup: some rules, some tools, nothing extreme.
CONTEXT TAX · EVERY TURN
~4.7k tokens
Moderate · 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 yopazerbot/brieltje/.claude ./rig-brieltje  # 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/implementer.md https://raw.githubusercontent.com/yopazerbot/brieltje/main/.claude/agents/implementer.md
$ curl -fsSL --create-dirs -o .claude/agents/reviewer.md https://raw.githubusercontent.com/yopazerbot/brieltje/main/.claude/agents/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 (2)

implementer
model: sonnet
Builds a change in Brieltje from a written plan that names the files, the approach and the checks. Use it for implementation work that is already decided, not for planning, security changes, the graph
reviewer
model: opus
Reviews a Brieltje change before it is pushed to main (which deploys to brieltje.be). Use it for the final review of a branch or of the merged result; give it the range of commits to review.

Similar rigs

copied ✓