by bgdnvk
clank your infra
# Add to your Claude Code skills
git clone https://github.com/bgdnvk/clankerEarly alpha.
First agent powering https://clankercloud.ai
Ask questions about your infra (and optionally GitHub/etc). Clanker is read-only: it calls CLIs/APIs and summarizes what it finds.
Repo: https://github.com/bgdnvk/clanker
Homebrew tap: https://github.com/clankercloud/homebrew-tap
brew tap clankercloud/tap
brew install clanker
make install
--no-cli-pager)brew install awscli
Copy the example config and edit it for your environments/providers:
cp .clanker.example.yaml ~/.clanker.yaml
alternatively you can do
clanker config init
Most providers use env vars for keys (see .clanker.example.yaml), e.g.:
export OPENAI_API_KEY="..."
export GEMINI_API_KEY="..."
If you run without ~/.clanker.yaml:
openai (unless you pass --ai-profile).--openai-key → OPENAI_API_KEY (also supports ai.providers.openai.api_key and ai.providers.openai.api_key_env if config exists).--ai-profile gemini-api): → (also supports and if config exists).--gemini-keyGEMINI_API_KEYai.providers.gemini-api.api_keyai.providers.gemini-api.api_key_envopenai defaults to gpt-5; gemini/gemini-api defaults to gemini-3-pro-preview.Clanker uses your local AWS CLI profiles (not raw access keys in the clanker config).
Create a profile:
aws configure --profile clankercloud-tekbog | cat
aws sts get-caller-identity --profile clankercloud-tekbog | cat
Set the default environment + profile in ~/.clanker.yaml:
infra:
default_provider: aws
default_environment: clankercloud
aws:
environments:
clankercloud:
profile: clankercloud-tekbog
region: us-east-1
Override for a single command:
clanker ask --aws --profile clankercloud-tekbog "what lambdas do we have?" | cat
Flags:
--aws: force AWS context/tooling for the question (uses the default env/profile from ~/.clanker.yaml unless you pass --profile)--profile <name>: override the AWS CLI profile for this run--ai-profile <name>: select an AI provider profile from ai.providers.<name> (overrides ai.default_provider)--maker: generate an AWS CLI plan (JSON) for infrastructure changes--destroyer: allow destructive AWS CLI operations when using --maker--apply: apply an approved maker plan (reads from stdin unless --plan-file is provided)--plan-file <path>: optional path to maker plan JSON file for --apply--debug: print diagnostics (selected tools, AWS CLI calls, prompt sizes)--agent-trace: print detailed coordinator/agent lifecycle logs (tool selection + i...