~ / rigs / junielton / harnu

junielton/harnu

A desktop cockpit to run and monitor multiple Claude Code sessions across various projects

↗ GitHub ★ 3 MIT updated 12d ago project Claude Code Claude plugin
share on X
ARCHETYPE
Skill Collector
Ten-plus skills loaded on demand. A procedural-knowledge library.
CONTEXT TAX · EVERY TURN
~13.0k tokens
Heavy · 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 junielton/harnu/.claude ./rig-harnu  # 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.

$ npx degit junielton/harnu/.claude/skills/harnu-awareness .claude/skills/harnu-awareness
$ npx degit junielton/harnu/.claude/skills/harnu-conductor .claude/skills/harnu-conductor
$ npx degit junielton/harnu/.claude/skills/local-ci .claude/skills/local-ci
$ npx degit <redacted> .claude/skills/conductor
$ npx degit <redacted>-verifier .claude/skills/delivery-verifier
$ npx degit <redacted>-watchdog .claude/skills/delivery-watchdog
$ npx degit junielton/harnu/resources/skills/skills/draft-to-prompt .claude/skills/draft-to-prompt
$ npx degit junielton/harnu/resources/skills/skills/grill-me .claude/skills/grill-me
$ npx degit junielton/harnu/resources/skills/skills/mission .claude/skills/mission
$ npx degit junielton/harnu/resources/skills/skills/one-by-one .claude/skills/one-by-one
$ npx degit <redacted>-delivery .claude/skills/orchestrate-delivery
$ npx degit junielton/harnu/resources/skills/skills/read-aloud .claude/skills/read-aloud
$ npx degit junielton/harnu/resources/skills/skills/report-back .claude/skills/report-back
$ npx degit junielton/harnu/resources/skills/skills/status .claude/skills/status
$ npx degit junielton/harnu/resources/skills/skills/step-by-step .claude/skills/step-by-step

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 (15)

Similar rigs

copied ✓