This is the edge of agentic intelligence — an enterprise-grade ecosystem for
running AI agents at scale in environments where a wrong move is a board-level
incident. It collects reusable skills, agents, rules, MCP references,
and supporting assets for AWS, Azure, OCI, GCP, Alibaba Cloud, Huawei Cloud,
Kubernetes, and Terraform — plus a cross-functional Legal + HR agentic ecosystem.
This is not just cloud infrastructure tooling. It is agentic coordination:
maestro routing, escalation-aware protocol, structured handoff between specialists,
and refusal-by-default safety on every irreversible action. Cloud is one domain it
operates in. Coordination, governance, and escalation are the product.
📊 Catalog at a glance
Catalog
Count
Skills
404
Agents
426
Providers
32
Install roles
21
Rules
1
MCP references
3
🧠 Skills = step-by-step workflows an AI assistant can follow.
🤖 Agents = reusable expert roles for review, architecture, and operations.
📏 Rules = durable instructions for a specific AI harness.
🔌 MCP references = trusted notes for connecting tools to real systems.
🗂️ Catalogs = machine-readable indexes so tools can discover everything.
📦 Available on npm:@raishin/vanguard-frontier-agentic is published on the public npm registry.
⚠️ ALPHA FINOPS BUNDLE: As of v1.8.0, this package includes 4 new experimental FinOps agents and 7 skills for cloud cost optimization, AI economics modeling, Kubernetes rightsizing, and FOCUS-spec normalization. All are marked lifecycle: experimental. See the board readiness memo for known limitations, risk mitigation, and 30-day diligence closure requirements. Use at your own risk in pre-production environments. Production deployment requires signed design-partner SOWs, Big 4 accounting validation, and SOC 2 Type II observation (≥150 days).
🛰️ Why Vanguard Frontier?
"Vanguard frontier" is not branding — it is an operating posture. This ecosystem
is built for the front line of agentic deployment, where AI agents touch real
production systems, real regulated data, and real legal exposure.
🏛️ Built for Fortune 50 / high-stakes environments. Every agent assumes
the blast radius is enterprise-scale: regulated data, audited controls, and
decisions that survive legal discovery. Refusal-by-default beats a fast path
to a board-level incident.
⚖️ The Legal + HR ecosystem is proof of cross-functional agentic
coordination. 28 specialist agents (Legal maestro + 12 specialists, HR
maestro + 14 specialists) and 3 cross-functional protocol skills demonstrate
that agents can hand off, escalate, and coordinate across organizational
boundaries — not just answer in isolation.
🧾 Audit-ready, privacy-preserving, escalation-aware by design. Every
review and live-guard agent emits a structured verdict (verdict,
evidence_level, blockers, safe_next_actions, open_questions) that maps
directly to SOC 2, PCI DSS, NIS2, NIST CSF, and ISO 27001 — no post-processing.
🛡️ Battle-tested against real compliance, governance, and risk workflows.
These patterns are exercised against live IAM mutations, KMS destruction,
litigation holds, RIF planning, and privacy reviews — the workflows where a
generic agent gets an organization sued.
The bar: an auditor, a regulator, or opposing counsel should be able to
read the agent's output and trace exactly who decided what, on what evidence,
and who approved the risk.
🧱 What's Inside — the three-layer agentic architecture
Vanguard Frontier is not a flat bag of prompts. It is a deliberate three-layer
system, and every domain — cloud providers, Kubernetes, marketing, Legal, HR —
follows the same shape.
Layer
Role
Examples
1. 🧭 Maestro (router)
Entry point. Classifies the request, routes to the right specialist, never executes risk itself.
How it flows: a request enters at the maestro, which routes to a
specialist. When a matter crosses a boundary — an HR investigation that
needs privileged Legal review, or a Legal hold that triggers an HR data freeze —
the cross-functional protocol carries a structured case capsule between
agents, preserving privilege, minimizing data, and recording the escalation path.
This is what "agentic coordination" means here: routing, protocol, and
escalation are first-class, not improvised.
🚀 Get Started
Pick the install path for your coding agent. Each dropdown is crystal-clear, step-by-step, and one-click plug-and-play where the harness supports it; the npm/export path works for everything else.
Kiro Powers UI is per-Power directory add — there is no single-command marketplace flow. This repo ships 14 Powers under powers/, one per provider, so Kiro users can add only what they need.
# 1. Clone this repo
git clone https://github.com/Raishin/vanguard-frontier-agentic
cd vanguard-frontier-agentic
# 2. In Kiro:# Open the Powers panel → "Add Custom Power" → "Local Directory"# Paste the absolute path to the Power(s) you need, one at a time:# /absolute/path/to/vanguard-frontier-agentic/powers/vanguard-aws# /absolute/path/to/vanguard-frontier-agentic/powers/vanguard-kubernetes# /absolute/path/to/vanguard-frontier-agentic/powers/vanguard-terraform
♊ Gemini CLI & Google Antigravity — skills framework via npm export
Antigravity reads skills from .agent/skills/<name>/SKILL.md (workspace) or ~/.gemini/antigravity/skills/<name>/ (global). There is no first-party marketplace install command — use the npm export to write skills + adapters into the right paths:
cross-platform-agent-template — scaffold for new cross-platform agents
For agent adapter files (.codex/agents/*.toml): after enabling the plugin, run npx vfa-export-agents --platform codex --all --repo . to write the 426 agent adapters into your repo
# 1️⃣ Install the package
npm install @raishin/vanguard-frontier-agentic@latest
# 2️⃣ Export agents for your role into your repo (claude-code shown — swap platform)
npx vfa-export-agents --platform claude-code --role cloud-security-engineer --repo .
# 3️⃣ Open your coding agent and reference the exported agent# "Use kubernetes-rbac-review-agent to audit this RBAC change."
Supports --platform: claude-code, codex, copilot, cursor, gemini, kiro, kiro-ide, kiro-cli. Supports --role, --agents, --all, --provider filters. See the Install Reference for the full argument matrix.
Install paths
There are now eight supported install paths — Claude Code plugin marketplace, GitHub Copilot CLI marketplace, Cursor plugin, Codex plugin marketplace, Kiro Powers, Gemini Antigravity skills, npm package + vfa-export-agents CLI, and the third-party skills CLI — each with different versioning, trust, and scope characteristics. See docs/integrations/skills-cli.md for the full trust matrix, verified flag syntax, pinning guidance, and pre-install inspection steps.
💰 skills/finops/finops-cloud-price-advisor — Fetch live prices from AWS, Azure, and OCI public pricing APIs; estimate costs for live environments or prototypes.
legal-hr-routing-protocol, legal-hr-case-capsule, legal-hr-risk-taxonomy (protocol skills, not agents)
⚖️ The Legal + HR cross-functional agentic ecosystem
Beyond cloud and platform agents, Vanguard Frontier ships a 28-agent cross-functional Legal + HR ecosystem plus 3 cross-functional protocol skills — proof that agentic coordination works across organizational boundaries, not just inside one cloud account.
Every Legal and HR agent is escalation-aware (knows when a matter must go to privileged counsel or a human owner), privacy-preserving (minimizes personal and sensitive data in every handoff), and audit-ready (emits the same structured verdict shape as the cloud live-guard agents). These agents advise on process and risk posture — they do not replace licensed legal counsel or qualified HR professionals, and they say so.
🟣 The .NET application review board
.NET is a free, cross-platform, open-source developer platform — runtime, libraries, and languages (C# is the most popular) — with ASP.NET Core as its lean, modular framework for modern cloud-based web services and EF Core as its lightweight, extensible data-access layer. The board is a dotnet-maestro router plus nine static-review specialists covering C#/runtime correctness, ASP.NET Core API architecture, identity and authorization, EF Core data access, test quality, CI/NuGet supply chain, performance/AOT/trimming, in-app OpenTelemetry wiring, and .NET Aspire cloud-native readiness — every agent reads source and sanitized configuration only and never builds, runs, migrates, or contacts a live system. These agents use provider: generic with a dotnet- ID prefix because .NET is a language/runtime, not a cloud provider — mirroring the existing non-cloud boards.
Every agent ships:
📄 AGENT.md — harness-neutral contract with guarded response shape
🗂️ metadata.json — schema-validated catalog entry
🔌 Harness adapters — claude-code + codex (EU providers); all 7 adapters for established providers
Use an agent when you need a role with judgment, not just a checklist.
📦 Install Reference
Everything you can install, and exactly how to install it. One section, no hunting.
🧭 How to pick what to install
🙋 I know my job function → use --role
🎯 I know the specific agent I want → use --agents
☁️ I work on one cloud provider only → add --provider to either of the above
💥 I want everything for a platform → use --all
🔍 I don't know what exists yet → use --list or --list-roles first
Print all agent IDs, providers, and names; then exit
--list-roles
—
🔍 standalone
Print role IDs with agent counts; then exit
--list-providers
—
🔍 standalone
List all providers with agent counts; then exit
--dry-run
—
➕ optional
Print the export plan without writing files
--no-skills
—
➕ optional
Skip companion skill bundling
🖥️ Platform reference
Each platform writes agent files to a different folder in your repo.
--platform value
AI harness
Installs into
claude-code
🤖 Claude Code (Anthropic)
.claude/agents/
codex
⚡ Codex CLI (OpenAI)
.codex/agents/
copilot
🐙 GitHub Copilot / VS Code
.github/agents/
cursor
🖱️ Cursor
.cursor/agents/
gemini
♊ Gemini CLI (Google)
.gemini/agents/
kiro
🔮 Kiro — both IDE + CLI adapters
.kiro/agents/
kiro-ide
🔮 Kiro IDE only
.kiro/agents/
kiro-cli
🔮 Kiro CLI only
.kiro/agents/
ℹ️ The exporter installs agent files only. It does not write repo-level guidance files (CLAUDE.md, AGENTS.md, .github/copilot-instructions.md, etc.). See docs/normalized-platform-matrix.md.
👤 Role reference
A role installs the curated set of agents a practitioner in that job function needs, across all cloud providers. Roles overlap intentionally — one agent may appear in multiple roles.
--role value
👤 Who it is for
🔢 Agents
☁️ What it covers
cloud-security-engineer
🔐 Security engineers, compliance teams, IAM owners
💾 SRE disaster recovery engineers, backup and restore owners
2
Velero live-guarded restore operations with pre-restore checklist, maestro router
# 🔍 See exactly which roles exist and how many agents each has
npx vfa-export-agents --list-roles
# 📦 Install a cloud role
npx vfa-export-agents --platform claude-code --role cloud-security-engineer --repo .
# ☁️ Install a cloud role but only for one provider
npx vfa-export-agents --platform claude-code --role cloud-security-engineer --provider azure --repo .
# ☸️ Install a Kubernetes specialist role
npx vfa-export-agents --platform claude-code --role kubernetes-admission-security-engineer --repo .
npx vfa-export-agents --platform claude-code --role kubernetes-network-engineer --repo .
☁️ Provider reference
Use --provider with --role to narrow the install to one cloud.
Build a practical AI workflow marketplace for secure cloud engineering.
This repository exists for teams that need to design, review, and operate cloud
systems where security and compliance are not optional extras.
The north star:
🛡️ Cloud architecture should be zero-trust by default, evidence-backed by
design, and understandable by engineers of any seniority.
That means every serious workflow should help engineers answer:
👤 Who is accessing what?
🔐 Why are they allowed?
🧾 Where is the evidence?
🚨 How do we detect abuse or drift?
🧯 How do we respond and recover?
📋 Which compliance obligation does this support?
🧬 Philosophy
This repo is opinionated. That is a feature, not a bug.
1. 🛡️ Zero trust beats implicit trust
Do not trust a network, cloud account, CI runner, agent, workload, or human just
because it is "inside" something.
Good assets should push for:
strong identity,
least privilege,
explicit authorization,
segmentation,
continuous verification,
logging and detection,
short-lived credentials where possible,
safe rollback paths.
2. 🧾 Compliance needs evidence, not vibes
SOC 2 Type 2, PCI DSS, NIS2, and NIST-style control frameworks are not passed by
good intentions. They require repeatable controls and evidence over time.
Good assets should produce or point to evidence:
policy decisions,
access reviews,
architecture diagrams,
ticket approvals,
logs and alerts,
backup and restore tests,
vulnerability and patch records,
incident response records,
change history.
3. 🔐 Least privilege is the default
If a workflow recommends broad admin access, it must explain why.
If it cannot explain why, it should not recommend it.
4. 🧪 Every claim needs a source or a validation path
AI-assisted automation should not become a fast path to production damage.
Dangerous actions need:
read-only discovery first,
explicit approval,
scoped credentials,
dry-run or plan mode where possible,
rollback notes,
post-change validation.
📋 Compliance compass
This repository is not a compliance product and does not replace auditors,
QSAs, legal counsel, or official standards.
It is a control-aware engineering toolbox. The assets should help teams
design and collect evidence for common security expectations across frameworks.
Every live-guard and review agent produces a structured verdict response (verdict, evidence_level, blockers, safe_next_actions, open_questions) that maps directly to SOC 2 CC6.1, PCI DSS Req 7, NIS2 Article 21, NIST CSF PR.AC-4, and ISO 27001 A.9.1.1 — no post-processing required. See docs/evidence-output-spec.md for the full control mapping and evidence retention guidance.
Framework / standard
What it pushes us to remember
Repo design implication
🔵 SOC 2 Type 2
Controls must operate over a period of time, especially around security, availability, confidentiality, processing integrity, and privacy trust service criteria.
Workflows should leave evidence trails, not just one-time fixes.
💳 PCI DSS
Cardholder data environments need scoped controls, secure configuration, access control, monitoring, vulnerability management, and testing.
Workflows should reduce scope, avoid broad access, and flag payment-data risk.
🇪🇺 NIS2
EU cybersecurity rules emphasize governance, risk management, incident reporting, supply-chain security, and management accountability.
Workflows should make ownership, reporting, and supplier/cloud dependencies explicit.
Assets should not stop at prevention; they should include detection, response, and recovery.
🏛️ NIST SP 800-207 Zero Trust
Access should be continuously evaluated and should not rely on implicit network trust.
Agents and skills should challenge flat networks, permanent credentials, and unverified trust boundaries.
Ruthless correction: NIS2 is the European cybersecurity directive. NIST
is a U.S. standards body. If someone says "NIST2 European compliance," they
probably mean NIS2 or they are mixing two different things.
🏗️ Architecture principles
Use these principles when creating or reviewing assets:
Principle
What good looks like
👤 Identity-first
Humans, workloads, agents, and CI/CD jobs have explicit identities.
🔐 Least privilege
Permissions are narrow, justified, and reviewable.
🧱 Segmented blast radius
Network, account, project, subscription, tenancy, and data boundaries are deliberate.
🧾 Evidence by design
The workflow naturally produces logs, approvals, diffs, plans, or reports.
🔎 Continuous monitoring
Detection is part of the design, not an afterthought.
🧯 Recoverability
Backups, restore tests, rollback, and incident response are considered upfront.
🧭 Source-grounded guidance
Official docs and live state beat memory and assumptions.
🤝 Human accountability
AI can assist, but owners still approve risk.
✅ Eval-driven development
This repository uses eval-driven development (EDD) to ensure quality and consistency.
Before implementing any new feature, agents, or skills:
Define evals first — What must pass? (capability evals + regression evals)
Implement — Build agents, skills, or features
Validate — Run the test suite and evals
Report — Document results in .claude/evals/<feature>.md
🗂️ Add or update catalog metadata in the matching catalog/*.json file.
✅ Run npm run validate.
🧯 Check safety — no secrets, no broad permissions without justification, no destructive actions without approval gates.
❓ FAQ
Skills vs agents — what's the difference?
A skill teaches your coding agent how to do a task (step-by-step workflow, CLI commands, reference material). An agent gives your coding agent a role with judgment — it loads the skill and adds a guarded response shape, approval gates, and a hardened permission model.
Do I need a cloud account to use these?
For reviewing architecture, writing IaC, or planning — no. For live-guard agents that execute against a real environment — yes, and they will ask you to confirm subscription/tenancy/principal before any mutation.
Can I use a skill or agent without the exporter CLI?
Yes. Copy the harness file for your platform from agents/<provider>/<id>/harnesses/ directly into your repo's agent folder. The CLI just automates that copy.
What is a "live guard" agent?
A live-guard agent operates against a real cloud environment. It enforces approval gates before any mutation, requires preflight evidence (what-if/plan/status output), and treats missing rollback design as a stop condition. Live guards are refusal-by-default — if target identity, approval state, or rollback posture is ambiguous, they stop and say so.
What does the FinOps price advisor actually do?
It fetches live on-demand prices from AWS Price List API, Azure Retail Prices API, and OCI public pricing API — all public, unauthenticated endpoints. It never needs billing credentials. Currency defaults to USD; other currencies are available via Azure's native currencyCode parameter or public exchange rate APIs for AWS/OCI.
Can I contribute new skills or agents?
Yes — see Contributing. The baseline requirement: the asset must be specific, source-backed, security-aware, and validated by npm run validate.
📚 Source anchors
Use official sources when writing security or compliance-sensitive assets:
Skills = workflows 🧠 286 across AWS · Azure · OCI · GCP · Alibaba · Huawei · Kubernetes · CNCF · Terraform
Agents = expert roles 🤖 289 with 7 harness adapters each
Rules = always-on 📏 harness-specific operating guidance
MCP = real connections 🔌 AWS · Azure · Oracle official servers
Catalog = searchable index 🗂️ machine-readable, hash-verified
❤️ Sponsors
Why Sponsor
Vanguard Frontier Agentic is a free, open-source marketplace of AI skills and agents for cloud operators — built on 70+ certifications across providers and 3 years of real enterprise architecture work across AWS, Azure, and OCI.
No VC funding. No company backing. One engineer, building in public.
In two weeks on npm: ~900 downloads. Socket.dev scores: Vulnerability 100, Quality 100, License 100. Every release ships through 17 validation gates, adversarial security audits, and property-based fuzz tests.
Your sponsorship directly funds the compute, API time, and research hours that turn new cloud providers, compliance frameworks, and security patterns into production-ready agents — free for everyone.
→ New cloud provider suites — each provider costs ~8–12 hours of research, agent design, security audit, and validation across 17 gates
→ Compliance coverage — GDPR, MLPS 2.0, FedRAMP, ISO 27001, SOC 2 mapped into agent guardrails and live-guard hard-stop conditions
→ Security audit cycles — adversarial multi-persona review, fuzz testing, OWASP / LLM Top 10 validation before every merge
→ New harness support — as AI coding tools evolve, agents stay current across Claude Code, Copilot, Codex, Cursor, Gemini, Kiro
→ Infrastructure — npm publishing, CI/CD, OpenSSF Scorecard, SLSA attestations, SBOM signing on every release
Sponsorship Tiers
☕ Cloud Supporter — $5/month
You believe free cloud tooling matters. Your name in the SPONSORS.md wall of thanks. Every contribution keeps the lights on.
🛡️ Agent Backer — $15/month
You use the agents and want to see them grow.
Name + link in SPONSORS.md
Priority response on GitHub Issues you open
Early access to release notes before they go public
🔧 Provider Sponsor — $50/month
You want a specific cloud or compliance gap closed faster.
Everything in Agent Backer
Vote on the next cloud provider or compliance framework to be added to the roadmap
Your GitHub handle credited in the provider README you helped fund
🏗️ Architecture Patron — $100/month
You run cloud workloads and this saves your team real time.
Everything in Provider Sponsor
One dedicated GitHub Discussion per month — ask me anything about cloud architecture, agent design, or compliance strategy
Logo / link in root README (individual or company)
🌐 Enterprise Tier — $500/month
You want coverage your team can rely on.
Everything in Architecture Patron
Direct input on the quarterly roadmap
Priority build of one cloud provider suite or compliance framework per quarter
Company logo in root README with featured placement
Private Slack / Discord channel access for your team
The Honest Version
This project is built in the hours before and after a full-time architecture role. Sponsorship doesn't make me rich — it covers API costs, compute time, and the research hours that keep the catalog growing past what I could sustain alone.
If you've installed the package, opened an agent, or just found value in knowing this exists — thank you. That's already enough.
Cloud and zero-trust agentic workflow marketplace for skills, agents, rules, MCP references, and compliance-aware architecture.
The npm package @raishin/vanguard-frontier-agentic receives a total of 31,340 weekly downloads. As such, @raishin/vanguard-frontier-agentic popularity was classified as popular.
We found that @raishin/vanguard-frontier-agentic demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago.It has 1 open source maintainer collaborating on the project.
Package last updated on 29 May 2026
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
OSV withdrew 157 OSV malware reports after automated false positives incorrectly flagged trusted npm and PyPI packages, sending bad records into tools that rely on OSV data.