Individual skill
google-cloud-solution-multi-agent-security
Designs, deploys, and secures Google Cloud Agent Gateway solutions. Use when the user needs to configure multi-agent security, ingress (CLIENT_TO_AGENT), or egress (AGENT_TO_ANYWHERE) patterns involving Model Armor, IAP, and Agent Registry. Don't use for general Cloud Load Balancing or basic VPC setup not related to Agent Gateways.
skills/cloud/google-cloud-solution-multi-agent-security/SKILL.md
Source commit 496fbede89dac1faf0d180a936bfc472b6fbf886
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 23,517
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- google Repository topic
- googlecloud Repository topic
- skills Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 14,961 bytesassets/agw-authz-extension.yamlasset · 275 bytesassets/agw-authz-policy.yamlasset · 325 bytesassets/agw-egress-config-run.yamlasset · 530 bytesassets/agw-egress-config.yamlasset · 247 bytesassets/agw-ingress-config.yamlasset · 255 bytesassets/iap-policy-multi-agent.jsonasset · 590 bytesassets/iap-policy.jsonasset · 469 bytesassets/main.tfasset · 2,421 bytesassets/model-armor-advanced.yamlasset · 386 bytesassets/model-armor-config.yamlasset · 353 bytesassets/model-armor-payload.jsonasset · 101 bytesassets/sgp-policy.yamlasset · 311 bytesreferences/attribution.mddoc · 1,974 bytesscripts/create_gke_dns_record.shruns · 287 bytesscripts/deploy_infrastructure.shruns · 1,052 bytesscripts/enforce_sgp_patch.shruns · 548 bytesscripts/fix_egress_iap.shruns · 226 bytesscripts/hybrid_vpn_agent.pyruns · 1,216 bytesscripts/multi_agent_cloud_run.pyruns · 1,760 bytesscripts/register_cloud_run_services.shruns · 1,065 bytesscripts/validate_ingress_unauth.shruns · 433 bytesscripts/verify_egress_policies.pyruns · 797 bytesscripts/verify_ingress_auth.shruns · 483 bytes
Read excerpt
# Agent Gateway multi-agent security
## Attribution
**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you
MUST read and follow the instructions in
[Usage Attribution](references/attribution.md).
## Critical Enforcement Rules & Rationale
* **Gcloud Release Tracks**: Always use the exact release tracks specified in
the commands (e.g., `gcloud beta network-services agent-gateways`). Omitting
these prefixes causes commands to fail because Agent Gateway features are
located in specialized, non-default namespaces.