Skill119 repo starsupdated today

harness-secrets

This skill provides three modes for managing GCP Secret Manager integration in CI/CD pipelines. The "check" mode validates GCP setup and authentication prerequisites before publishing. The "fetch" mode retrieves secret values for pipeline use. The "validate-token" mode confirms an NPM token is active by running npm whoami without executing a full publish. Use this to rotate short-lived credentials at publish time and verify token validity before release.

View source Repository: agent-harness-generator

Install in Claude Code

Copy

git clone --depth 1 https://github.com/ruvnet/agent-harness-generator /tmp/harness-secrets && cp -r /tmp/harness-secrets/.claude-plugin/skills/harness-secrets ~/.claude/skills/harness-secrets

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# harness-secrets

> Codex skill for GCP Secret Manager — check / fetch / validate-token.

## Modes

### check
Validates the full GCP setup (`gcloud` on PATH, active project, auth principal, secret exists, WIF pool present). Use this when bootstrapping a new GCP project for publish.

```
/harness-secrets mode=check
/harness-secrets mode=check secret=NPM_TOKEN_DEV
/harness-secrets mode=check project=my-gcp-project secret=NPM_TOKEN
```

### fetch
Fetches a secret value to stdout. Use in pipelines:

```
/harness-secrets mode=fetch secret=NPM_TOKEN
/harness-secrets mode=fetch secret=GH_TOKEN version=3
```

### validate-token
Fetches `NPM_TOKEN` and runs `npm whoami` against the registry. No publish — just confirms the token isn't revoked. Use this BEFORE you tag a release.

```
/harness-secrets mode=validate-token
/harness-secrets mode=validate-token secret=NPM_TOKEN_STAGING
```

## Equivalent CLI

```bash
harness secrets check --secret=NPM_TOKEN
harness secrets fetch NPM_TOKEN --version=3
harness secrets validate-token
```

## Why this exists

So you can refresh + verify the publish-time GCP secret WITHOUT triggering a real publish.