neckbeard plugin
neckbeard turns an app repo into cloud infrastructure built from tested OpenTofu modules, with the monthly bill priced up front
- 278 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The plugin generates infrastructure and CI files, and applying them stays with a human.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/neckbeardDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The plugin generates infrastructure and CI files, and applying them stays with a human.
This is third-party code. Review the repository files before installing.
What it does
The plugin reads an app repo: Dockerfiles, ports, environment variables, health endpoints. The result is an `app-profile.yaml` where every fact carries a file and line. Open questions (traffic, tolerable downtime, existing or new database) go to a human, and planning waits until they are answered. `/neckbeard:estimate` then plans against the module catalog and prints a monthly price table, and `/neckbeard:sync` scaffolds infrastructure, pipelines and Kubernetes manifests and validates them. AWS, GCP and Azure are covered with GitHub Actions or GitLab CI, plus Hetzner with docker compose.
Who it is for. Developers without a dedicated ops person who must ship a containerised app to the cloud and see the bill before the first `apply`.
Good fit when
- A containerised app goes to AWS, GCP or Azure for the first time.
- You want to compare serverless and Kubernetes cost for one app.
- An agent would write Terraform on its own and you want it limited to ready modules.
- Infrastructure review should run as an ordinary pull request with files in the repo.
Not a fit when
- The app does not fit one container image, up to ten processes, Postgres and object storage.
- The cloud catalog must provision Redis: it has no such module.
- You expect the agent to get cloud credentials: it never receives them.
Example request
Run `/neckbeard:analyze`, ask the traffic questions, then `/neckbeard:estimate serverless vs kubernetes`.Limitations
The catalog covers one workload shape: a container image, up to ten HTTP, worker and cron processes, Postgres, object storage and secrets. The cloud catalog explicitly refuses to provision Redis. The first plugin command installs the `neckbeard` CLI from a sha256-verified release or via `go install`. Cost estimates and validation lean on Infracost, OpenTofu and Checkov, and without them some prices and checks are reported as not exercised. A human performs the first environment bootstrap from `docs/bootstrap.md`. The Disco VPS lane is experimental.
How to disable. Run `/plugin uninstall neckbeard` and delete the `neckbeard` binary if you installed it. Generated infrastructure files live in the repo and are removed separately.
FAQ
Does the agent get cloud keys?
No. A human performs the bootstrap with their own credentials from the generated `docs/bootstrap.md`.
Will sync overwrite my edits?
No. `/neckbeard:sync` refuses to overwrite files you have touched.
What does `/neckbeard:doctor` do?
It installs the CLI if missing and reports which of Infracost, OpenTofu and Checkov are present.
Which clouds and CI systems are supported?
AWS, GCP and Azure with GitHub Actions or GitLab CI, plus a Hetzner lane on docker compose.
What if questions stay unanswered?
Planning refuses to run while any app question remains open.
Discussion
No questions or reviews yet.
Related
PluginsPlugin with one skill: the agent prepares a project, deploys a container to the Cloudish cloud and returns the live URL.
Terragrunt organizes OpenTofu and Terraform configurations into units with shared inputs, dependencies and ordered execution.
A plugin that reminds the agent of free-tier limits and paid traps in cloud services before deploys, without blocking any command.
Terraform Skill
Terraform & OpenTofu Skill for AI Agents
A Terraform and OpenTofu best-practices skill: tests, modules, state, CI/CD and security scanning for AWS, Azure and GCP
A pattern library and skill set for recurring agent loops: issue triage, dependency cleanup, PR babysitting
Official Flux CD skills: Flux answers, manifest generation, GitOps repository audit and debugging of live-cluster failures
README in short
The agent works out what the app needs, while deterministic Go code renders infrastructure from versioned modules.