RayStack v0.1 · Open source, MIT

Infrastructure reviews your coding agent can run.

Point your agent at a repo and type /raystack. You get a ranked findings report on cost, security, bottlenecks, deploys, scaling, or the database. Every finding has evidence and a fix you apply yourself. It's what I check when I audit someone's stack, written down as agent skills.

View on GitHub Install

Install

Pick your agent

You need bash and jq. The PDF export also needs Chrome or Chromium and npx.

Claude Code

/plugin marketplace add HarunRRayhan/raystack
/plugin install raystack@raystack

Then type /raystack in the repo you want reviewed.

Codex

codex plugin marketplace add HarunRRayhan/raystack
codex plugin add raystack@raystack

Or run ./install.sh --agent codex from a clone.

Cursor

./install.sh --agent cursor

Run it from a clone. It copies the skills to ~/.cursor/skills/.

Grok

grok plugin marketplace add HarunRRayhan/raystack
grok plugin install raystack --trust

Not tested end to end yet. ./install.sh --agent grok works too.

Any other agent

./install.sh --agent custom --dir /path/to/skills

--dry-run shows what it would do. --uninstall removes the seven skills.

Skills

Seven skills, one router

/raystack looks at the repo, recommends reviews, and asks once which ones to run. You can also name a review directly.

raystack: The entry point. Picks the reviews that fit this repo and runs them.
aws-billing-review: AWS spend, with savings ranked in $/mo.
aws-security-review: IAM, public exposure, logging, and secrets on AWS.
aws-bottleneck-review: Throttling, limits, quotas, and single points on the request path.
infra-review: Deploys, rollback, backups, monitoring, and exposure on any platform.
scaling-review: What breaks first at 10x and 100x load.
database-review: Queries, indexes, migrations, backups, connections, and bloat.

Safety

Read-only by design

No review changes anything live. Fixes come back as diffs or as commands for you to run.

In Claude Code, a guard hook checks every shell command during a review. Cloud and database CLIs get read verbs only, and deploy tools are blocked. The guard is a seatbelt, not a sandbox. Cursor, Codex, and Grok follow the same rules, but nothing enforces them there.

So run reviews with read-only credentials: AWS ReadOnlyAccess or ViewOnlyAccess, and a read-only database role. That's the real boundary.

Output

What you get back

Each review writes reviews/YYYY-MM-DD-<skill>.md in your repo. It has a short summary, the inputs it used and the ones it lacked, and findings ranked Critical to Low. Each finding has evidence, a fix, and an estimated $/mo where one can be worked out. Want a PDF for a client or your boss? The review offers one at the end.

No live access? A review still works from your IaC and code, marks those findings unconfirmed, and lists what it needs from you.

Want me to look at it myself?

RayStack covers the checks I run first. For a hands-on audit of your stack, book a consultation.

Book a consultation