~ / rigs / chasedputnam / go-kiro-gateway

chasedputnam/go-kiro-gateway

An API gateway proxy for Kiro API (Amazon Q Developer / AWS CodeWhisperer)

↗ GitHub ★ 12 AGPL-3.0 updated 1mo ago project Claude CodeCodex
stack: DockerGo
share on X
ARCHETYPE
Orchestrator
A bench of specialised subagents. The main agent mostly delegates.
CONTEXT TAX · EVERY TURN
~7.0k tokens
Heavy · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details
Quality 3/100 Guardrails v2

Copy this rig

# review before running: this installs third-party code
$ npx degit chasedputnam/go-kiro-gateway/.claude ./rig-go-kiro-gateway  # 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 chasedputnam/go-kiro-gateway/.claude/skills/code-review .claude/skills/code-review
$ npx degit chasedputnam/go-kiro-gateway/.claude/skills/dev .claude/skills/dev
$ npx degit chasedputnam/go-kiro-gateway/.claude/skills/spec .claude/skills/spec
$ curl -fsSL --create-dirs -o .claude/agents/code-reviewer.md https://raw.githubusercontent.com/chasedputnam/go-kiro-gateway/main/.claude/agents/code-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/pipeline-engineer.md https://raw.githubusercontent.com/chasedputnam/go-kiro-gateway/main/.claude/agents/pipeline-engineer.md
$ curl -fsSL --create-dirs -o .claude/agents/product-owner.md https://raw.githubusercontent.com/chasedputnam/go-kiro-gateway/main/.claude/agents/product-owner.md
$ curl -fsSL --create-dirs -o .claude/agents/project-manager.md https://raw.githubusercontent.com/chasedputnam/go-kiro-gateway/main/.claude/agents/project-manager.md
$ curl -fsSL --create-dirs -o .claude/agents/quality-engineer.md https://raw.githubusercontent.com/chasedputnam/go-kiro-gateway/main/.claude/agents/quality-engineer.md
$ curl -fsSL --create-dirs -o .claude/agents/security-reviewer.md https://raw.githubusercontent.com/chasedputnam/go-kiro-gateway/main/.claude/agents/security-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/software-architect.md https://raw.githubusercontent.com/chasedputnam/go-kiro-gateway/main/.claude/agents/software-architect.md
$ curl -fsSL --create-dirs -o .claude/agents/software-engineer.md https://raw.githubusercontent.com/chasedputnam/go-kiro-gateway/main/.claude/agents/software-engineer.md
$ curl -fsSL --create-dirs -o .claude/agents/teleport-expert.md https://raw.githubusercontent.com/chasedputnam/go-kiro-gateway/main/.claude/agents/teleport-expert.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 (3)

Subagents (9)

code-reviewer
model: sonnet
Code reviewer. Use for reviewing pull requests and code changes for correctness, clarity, security, test coverage, and adherence to project conventions.
pipeline-engineer
model: sonnet
CI/CD and build pipeline specialist. Use for GitLab CI configuration, Packer builds, Ansible roles, and container image pipeline work.
product-owner
model: opus
Expert product owner. Use for creating requirements, defining acceptance criteria, and evaluating whether a solution meets user and business needs.
project-manager
model: sonnet
Expert project manager and software engineer. Use for planning tasks and work, identifying risks and blockers, tracking progress, and coordinating across workstreams.
quality-engineer
model: sonnet
Quality engineer and tester. Use for designing test strategies, writing tests, identifying coverage gaps, and evaluating whether a feature is ready to ship.
security-reviewer
model: opus
Security specialist. Use for auditing authentication, authorization, input validation, and vulnerability analysis. Read-only — never makes changes.
software-architect
model: opus
Chief software architect. Use for system and implementation design, architectural decisions, technology selection, and evaluating trade-offs across components or services.
software-engineer
model: sonnet
Expert software engineer. Use for implementing features, fixing bugs, writing tests, and refactoring code across the stack.
teleport-expert
model: sonnet
Teleport infrastructure specialist. Use for questions about Teleport configuration, app service agents, tbot Machine ID, join tokens, and Kubernetes deployment of Teleport components.

Similar rigs

copied ✓