Borrowing it
Nothing to install: this file belongs to AlphaBitCore/nexus-gateway. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AlphaBitCore/nexus-gateway/main/.claude/skills/build-ami/SKILL.mdgit clone --depth 1 https://github.com/AlphaBitCore/nexus-gatewayWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/alphabitcore/nexus-gateway/build-ami)<a href="https://agentmods.dev/skills/alphabitcore/nexus-gateway/build-ami"><img src="https://agentmods.dev/badge/skills/alphabitcore/nexus-gateway/build-ami.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 114 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 62 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00143 | $0.02053 |
| Opus 5 | $0.00072 | $0.01026 |
| Sonnet 5 | $0.00029 | $0.00411 |
| Haiku 4.5 | $0.00014 | $0.00205 |
Grade A, and why
build-ami scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
build-ami
Build and register the Nexus Gateway single-instance appliance AMI from nexus-ami/.
nexus-ami/build.sh cross-compiles the 4 Go services (linux/amd64), builds the Vite UI, bundles
Prisma, tarballs artifacts/, then runs packer init && packer build nexus.pkr.hcl. Packer launches
one AL2023 x86_64 EC2 instance, uploads the tarball, runs install.sh + harden.sh, snapshots, and
registers the AMI. Full build ≈ 1 hour (the valkey-search C++ compile dominates).
⚠️ The two non-obvious traps (read first)
- vCPU quota. The committed default instance type is
m5.4xlarge= 16 vCPU. The EC2 Running On-Demand Standard instances quota (L-1216C47A) defaults to 16 on fresh accounts, and m5/c5/t3/r5 all share that bucket. Any already-running instance leaves <16 free, so a default./build.shdies in ~11s at "Launching a source AWS instance" withVcpuLimitExceeded: ... current vCPU limit of 16. Fix: build onr5.2xlarge(8 vCPU / 64 GB) via-var instance_type=r5.2xlarge. - valkey-search is RAM-bound, not CPU-bound.
install-valkey.shcompiles valkey-search from source (gRPC/Protobuf/Abseil/ICU submodules), capped at--jobs=4. It needs ~48–64 GB RAM — 32 GB hosts (t3.2xlarge / r5.xlarge / m5.2xlarge) get silently OOM-killed mid-compile (sshd dies before any error is logged → confusing SSH failure after ~10 min). So when dropping vCPU to fit the quota, drop to a memory-heavyr5, never a smallerm5.r5.2xlarge(8 vCPU / 64 GB) is the sweet spot: fits a 16-vCPU quota and keeps the RAM headroom. Never compile valkey-search on <48 GB.
There is no AL2023 prebuilt for valkey-search (1.2.0 is source-only; the official valkey/valkey-bundle
image is Debian/glibc-incompatible with the AL2023 appliance), so the source compile is mandatory.
postgres/nats/node already install prebuilt — prefer install over compile wherever a suitable build exists.
Standard build (recommended path)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 116 lines · 143 tokens per session scan A f1ed940e396b
build-ami is a skill published in the GitHub repository AlphaBitCore/nexus-gateway (23 stars, last pushed 6d ago), licensed Apache-2.0. It adds 143 tokens to every session and 2,053 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
cli-backup-sync
Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.
omni-sync-cloud
Synchronise OmniRoute configuration, provider connections, and settings to/from cloud storage. Manage cloud worker authentication and remote backup targets.
cli-tunnel
Start and stop tunnel connections (ngrok, Cloudflare, custom) from the CLI. Inspect active tunnel URLs, configure authentication, and test external reachability.
omni-tunnels
Create and manage secure tunnels (ngrok, Cloudflare Tunnel, custom) to expose OmniRoute to the internet or share access with remote agents and CI pipelines.
defenseclaw-ops
Manage DefenseClaw enterprise security - scan components, manage tool permissions, view alerts, configure guardrails.
aws-security-audit
AWS security auditing — IAM users/roles/policies, CloudTrail API events, security posture analysis. Use when auditing IAM permissions, investigating security incidents, checking MFA compliance, or tracing API activity in CloudTrail.