research
CommandStart or resume an academic research project — idea through literature, methodology, writing, feedback, and publishing
Read-only inventory of global Secret Manager names.
> /plugin marketplace add GRCEngClub/claude-grc-engineering
name: GCP Secret Metadata List description: Read-only inventory of global Secret Manager names.
Run only on an explicitly authorized project and only when the operator has approved sharing metadata with the agent. Secret names and project IDs can be sensitive. Do not request or handle secret values.
Install and authenticate the Google Cloud CLI outside the agent. Enable Secret Manager and grant the calling principal `secretmanager.secrets.list` on the project, without granting secret payload access solely for inventory. Run:
node ${CLAUDE_PLUGIN_ROOT}/scripts/list.js PROJECT_IDThe project ID is mandatory; no implicit project is used. The command invokes `gcloud secrets list` for global secrets, letting gcloud handle pagination, and outputs only project ID and resource names. It discards other returned fields, provider stderr and malformed responses. It does not enumerate regional secrets, versions, rotation, IAM policies or payloads. For one secret's version and rotation metadata, use `/gcp-secret-metadata:history` with separate authorization. Failures return nonzero without partial results. Output is sensitive inventory: store or share it only according to the organization's policy. This inventory command does not inject secrets, produce findings or integrate with gcp-inspector. The separate operator-only `/gcp-secret-metadata:run` command documents the runtime injection helper.
For numeric resource names, the command verifies the mapping with `gcloud projects describe PROJECT_ID`. This requires `resourcemanager.projects.get` on that project, which may not be granted to a secrets-only principal. No broader role is required; if lookup is denied or invalid, the command fails closed without inventory output. Textual names matching the requested ID do not require this lookup. The same restriction applies to the history command.
References: [gcloud secrets list](https://cloud.google.com/sdk/gcloud/reference/secrets/list), [Secret Manager list API and IAM permission](https://cloud.google.com/secret-manager/docs/reference/rest/v1/projects.secrets/list).
Open-source GRC Engineering resource for Claude. claude-grc-engineering turns technical evidence from cloud, SaaS, code, and security tools into framework-aligned findings, gap reports, remediation guidance, evidence packages, and OSCAL workflows.
Start or resume an academic research project — idea through literature, methodology, writing, feedback, and publishing
Query AWS for compliance-relevant configuration across IAM, S3, CloudTrail, EBS, and emit findings conforming to the v1 contract.
Install the frdocx-to-froscal-ssp Python pipeline and verify its dependencies. Idempotent.
Retrieve a single AWS Secrets Manager secret value to stdout or a 0600-permission file. Opt-in retrieval mode — never writes to…
Read metadata, version states and rotation schedule for one global secret.
Audit a file, directory, or whole repo for insecure default configuration: fallback secrets, default credentials, fail-open…
Check text against AGT prompt-injection, context-poisoning, and MCP threat detectors.
Show which external bug-bounty tools are installed on this machine and print install hints for the missing ones. Curated from…