research
CommandStart or resume an academic research project — idea through literature, methodology, writing, feedback, and publishing
Read metadata, version states and rotation schedule for one global secret.
> /plugin marketplace add GRCEngClub/claude-grc-engineering
name: GCP Secret Metadata History description: Read metadata, version states and rotation schedule for one global secret.
Obtain explicit authorization for this project and secret, including approval to share sensitive identifiers and metadata with the agent. Do not request or handle secret values. Authenticate gcloud outside the agent. The principal needs `secretmanager.secrets.get` and `secretmanager.versions.list`; payload access is not needed. Specify the project explicitly to prevent accidental cross-project collection.
node ${CLAUDE_PLUGIN_ROOT}/scripts/history.js PROJECT_ID SECRET_IDThe script retrieves the secret metadata and all version pages for that single global secret. It outputs resource names, available creation/expiration and version destruction timestamps, version states, and the rotation schedule, if present. Labels, annotations, provider diagnostics and other fields are omitted. It does not access payloads, retrieve IAM policies or evaluate controls. Failed or malformed calls return no partial output. A missing rotation object is shown as null, not as evidence of compliance or noncompliance. GCP rotation schedules send notifications; they do not themselves prove a credential was rotated. The two calls are not an atomic snapshot. Regional secrets are not supported. For numeric resource names, the command verifies the project ID and number via `gcloud projects describe PROJECT_ID`, requiring `resourcemanager.projects.get` on that project in addition to the secret permissions. A secrets-only principal may lack this permission; no broader role is required. Denied or invalid lookup fails closed with no output. Matching textual names do not trigger a lookup. Store or share this sensitive inventory only under organizational policy.
Use alongside `/gcp-inspector:collect` for the same explicitly selected project; this is separate metadata, not a fabricated finding or automatic integration. Terraform scans should never consume secret values or untrusted secret metadata as configuration. No automatic Terraform integration is provided.
References: [Secret metadata](https://cloud.google.com/secret-manager/docs/reference/rest/v1/projects.secrets), [version metadata](https://cloud.google.com/secret-manager/docs/reference/rest/v1/projects.secrets.versions), [version list](https://cloud.google.com/sdk/gcloud/reference/secrets/versions/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…
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…