volcengine-identity-access-control

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Security

Grade A, and why

volcengine-identity-access-control 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 yesterday.

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.

plugins/volcengine-identity-access-control/.claude-plugin/plugin.json · 27 lines

What it actually says

{
  "name": "volcengine-identity-access-control",
  "description": "Design and establish Volcengine landing zones, organizations, identity, account factories, and governance baselines.",
  "version": "1.1.2",
  "author": {
    "name": "Volcengine Team"
  },
  "homepage": "https://github.com/volcengine/volcengine-skills",
  "repository": "https://github.com/volcengine/volcengine-skills",
  "license": "MIT",
  "keywords": [
    "volcengine",
    "cloud",
    "身份与访问控制",
    "identity",
    "access control",
    "iam",
    "landing zone",
    "组织",
    "账号工厂",
    "volcengine-landing-zone"
  ],
  "skills": [
    "./skills/"
  ]
}

Changes

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.

Related

Other plugins, from other repositories