📦

using-sops

Name: using-sops
Author: jssblck

コンテンツリビジョン r1 重大 ⚙️ 外部コマンド🌐 ネットワークアクセス📁 ファイルシステムへのアクセス🔑 環境変数

Manage SOPS Secrets in Repositories

Encrypted repository secrets require careful commands, keys, and environment handling. This skill guides SOPS workflows through an existing pnpm secrets wrapper.

対応: Claude Codex Code(CC)

⚠️ 38 不十分

Maintain this Skill? Claim it ⚠️ 38 不十分

この Skill を自動インストールしないでください。

基準ポリシーにより、インストール操作の前にオペレーターのレビューが必要です。

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。

エージェントリクエスト

Review the Skillstore skill "using-sops" from https://skillstore.io/skills/jssblck-using-sops.md and its manifest at https://skillstore.io/api/skills/jssblck-using-sops/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

Markdown詳細 GET /skills/jssblck-using-sops.md 署名済み manifest GET /api/skills/jssblck-using-sops/manifest 署名済み lockfile GET /api/skills/jssblck-using-sops/lockfile

テストする

「using-sops」を使用しています。 Retrieve the development Stripe key without showing other secrets.

期待される結果:

The assistant identifies the repository wrapper, requests confirmation, retrieves only the named value, and avoids echoing unrelated decrypted data.

「using-sops」を使用しています。 Add a required API endpoint to every accessible environment.

期待される結果:

The development secret and environment schema are updated.
Production remains unchanged because elevation is unavailable.
The deployment requirement is recorded for review.

「using-sops」を使用しています。 Rotate a lost production recipient.

期待される結果:

The assistant lists recipient replacement, file re-encryption, value rotation, deployment updates, verification, and encrypted history exposure.

セキュリティ監査

重大

v1 • 2026/8/23 バージョン別レポートを開く

The skill intentionally grants agents broad access to encrypted development secrets and supports persistent production elevation. The most serious design stores a shared private key in persistent cloud environment variables, creating cross-project credential exposure.

スキャンされたファイル

272

解析済み行数

レビュー項目

誤検知を無視

確認済みのセキュリティ上の懸念 (8)

重大

references/setup.md:53-65 references/sops-notes.md:51-56

Private Key Stored in Non-Secret Cloud Variables

The setup places a reusable age private key in persistent cloud environment variables, including fields documented as unsuitable for credentials. Redaction limitations are acknowledged.

The instructions explicitly require SOPS_AGE_KEY in persistent environment variables and state that one platform advises against credentials there.

高

SKILL.md:3

Environment file access

description: Use when a repo has .sops.yaml and secrets/<env>.env, or a pnpm secrets script. Covers

The skill's declared purpose includes reading and writing encrypted environment secrets. This is intentional sensitive-data access with substantial impact if misused.

高

SKILL.md:21

Environment file access

| `agent` | user-wide | `~/.config/sops/age/keys.txt` on every machine agents run on; `SOPS_AGE

The line places an age private key in SOPS_AGE_KEY for cloud agents. Environment exposure can reveal a credential that decrypts multiple projects.

高

SKILL.md:45

Environment file access

Prod secrets need elevation. When a task requires reading or writing `prod.env`:

The workflow enables reading and writing production secrets after elevation. This is a real high-impact capability even though user participation is required.

高

SKILL.md:54

Environment file access

When you add a variable, add it to the env schema and to every `secrets/<env>.env` you can

The instruction directs the agent to modify every decryptable environment secret file. A mistaken or malicious change can affect multiple deployments.

高

SKILL.md:32-40

Unprompted Bulk Development Secret Access

The skill authorizes agents to show, modify, delete, and execute with all development secrets without user confirmation. This can expose or corrupt credentials beyond the immediate task.

The instruction explicitly says agents may manage development secrets without asking and includes a command that reveals everything decrypted.

高

SKILL.md:21-28 references/setup.md:49-51

Shared Cross-Project Decryption Identity

One agent private key is shared across every project and installed for all agent sessions. Compromise of one machine or session exposes every development file using that recipient.

Both files explicitly describe a user-wide identity shared by every project and accessible to any agent session on the machine.

高

SKILL.md:45-52 references/setup.md:118-119

Persistent Production Elevation Artifact

Production elevation remains active until a checkout file is manually deleted. A stale or copied checkout can retain production decryption access longer than intended.

The workflow states that elevation persists until manual deletion and has no timeout, session binding, or automatic cleanup.

機能レビュー項目 (8)

これらは、このスキルに期待される可能性のある実際のローカル機能であるため、レビューが必要ですが、確認済みの悪意ある動作としてはカウントされません。

高

references/setup.md:81

sudo privilege escalation

sudo mkdir -p /etc/credstore.encrypted

This command creates a root-owned system credential directory with sudo. It is legitimate administration, but it changes privileged host state.

高

references/setup.md:82

sudo privilege escalation

printf '%s' 'AGE-SECRET-KEY-1...' | sudo systemd-creds encrypt --name=age-prod - /etc/credstore.encr

This sudo command installs a production age private key as a system credential. Substituting the real key can expose it through shell history.

高

references/setup.md:13

Hardcoded URL

curl -fsSL https://github.com/FiloSottile/age/releases/download/v1.3.1/age-v1.3.1-linux-amd64.tar.gz

The command streams a remote archive directly into tar without integrity verification. A compromised response could write attacker-controlled files before review.

高

references/setup.md:44

Hidden file in home directory

install -m 600 /dev/stdin ~/.config/sops/age/keys.txt <<'EOF'

This instruction persists an age private key in the user's SOPS configuration. Mode 600 limits access, but every process running as that user can use the key.

高

references/setup.md:44

Hidden file access

install -m 600 /dev/stdin ~/.config/sops/age/keys.txt <<'EOF'

This instruction persists an age private key in the user's SOPS configuration. Mode 600 limits access, but every process running as that user can use the key.

高

SKILL.md:21

Hidden file in home directory

| `agent` | user-wide | `~/.config/sops/age/keys.txt` on every machine agents run on; `SOPS_AGE

The documented path stores a shared decryption key on every agent machine. Any agent process under that user can decrypt development secrets across projects.

高

SKILL.md:21

Hidden file access

| `agent` | user-wide | `~/.config/sops/age/keys.txt` on every machine agents run on; `SOPS_AGE

The skill explicitly relies on agents reading the user-wide SOPS key location. This grants broad filesystem-mediated access to development secrets.

中

references/setup.md:11

Hardcoded URL

curl -fsSL -o ~/.local/bin/sops https://github.com/getsops/sops/releases/download/v3.13.3/sops-v3.13

The instructions download an executable from GitHub and immediately mark it executable without checksum or signature verification. A compromised release path could execute attacker code.

リスク要因

⚙️ 外部コマンド (25)

🌐 ネットワークアクセス (2)

references/setup.md:11 references/setup.md:13

📁 ファイルシステムへのアクセス (15)

references/setup.md:11 references/setup.md:12 references/setup.md:14 references/setup.md:42 references/setup.md:44 references/setup.md:11 references/setup.md:12 references/setup.md:14 references/setup.md:42 references/setup.md:44 references/setup.md:44 references/sops-notes.md:7 references/sops-notes.md:7 SKILL.md:21 SKILL.md:21

🔑 環境変数 (3)

references/sops-notes.md:31 SKILL.md:9 SKILL.md:69

監査者: codex

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く

レポートリンクをコピー

https://skillstore.io/skills/jssblck-using-sops/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdownバッジ

[![Skillstore security assessment](https://skillstore.io/badges/skills/jssblck-using-sops/security.svg)](https://skillstore.io/skills/jssblck-using-sops?utm_source=security_passport_badge)

HTMLバッジ

<a href="https://skillstore.io/skills/jssblck-using-sops?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/jssblck-using-sops/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

埋め込みカード

<iframe src="https://skillstore.io/embed/skills/jssblck-using-sops.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

学術引用 (APA · BibTeX · CFF)

APA形式の引用

jssblck. (2026). using-sops security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/jssblck-using-sops/audits/1

BibTeX形式の引用

@techreport{jssblck-jssblck-using-sops-2026,
  author = {jssblck},
  title = {using-sops security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/jssblck-using-sops/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "using-sops security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "jssblck"
date-released: "2026-08-23"
url: "https://skillstore.io/skills/jssblck-using-sops/audits/1"
identifiers:
  - type: other
    value: "skillstore:jssblck-using-sops:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore スコア

このスコアの理由証拠の信頼度: 低

アーキテクチャ

保守性

コンテンツ

コミュニティ

仕様準拠

作成できるもの

Update Development Configuration

Inspect or change an encrypted development variable through the repository wrapper.

Configure Deployment Secrets

Prepare production decryption and service startup while keeping the key outside application files.

Rotate SOPS Recipients

Replace a lost or compromised age recipient and re-encrypt affected secret files.

これらのプロンプトを試す

Inspect One Development Variable

Use the repository secrets wrapper to retrieve [VARIABLE] from development. Explain the command first and avoid displaying unrelated values.

Add a Development Secret

Add [VARIABLE] to the development secrets and environment schema. Confirm before changing files and report any environment you cannot decrypt.

Run a Command With Secrets

Run [COMMAND] with development secrets through the repository wrapper. Verify the command scope and do not print decrypted values.

Plan Recipient Rotation

Review the SOPS recipients for [PROJECT]. Propose a rotation plan for [COMPROMISED_RECIPIENT], including affected files, approvals, re-encryption, and credential replacement.

ベストプラクティス

Use the repository wrapper instead of calling SOPS directly.
Request approval before revealing, changing, or executing with any secret.
Rotate both recipients and decrypted values after a private key leak.

回避

Do not print complete decrypted files when one variable is sufficient.
Do not place personal or production private keys in tracked files, logs, or cloud agent environments.
Do not leave production elevation active after the approved operation.

よくある質問

What repository layout does this skill expect?

It expects .sops.yaml, encrypted secrets files, and a pnpm secrets wrapper such as tools/secrets.ts.

Can it work without an age private key?

It can create files for configured public recipients, but decryption and editing require an authorized private key.

Does it call SOPS directly?

It instructs agents to use the repository wrapper when one exists.

How are production secrets protected?

Production uses a project-specific identity and requires checkout elevation. The documented elevation remains active until manually removed.

Can it rotate a compromised recipient?

It guides recipient replacement, SOPS updatekeys, commit review, and rotation of every value exposed by the old key.

Is cloud agent key storage safe?

The documented environment-variable approach is high risk. Use scoped, short-lived credentials in a supported secret store instead.

開発者情報

作成者

jssblck

ライセンス

MIT

Skillstore リビジョン

バージョンに関する注意

作者はバージョンを宣言していません。

リポジトリ

https://github.com/jssblck/agents/tree/4658295e88faed205cc134edf987f7ea4e0c8ea4/skills/using-sops

参照

0139ec01bdea5a1eaac3b0e3c90753dbfe65aaa1

メンテナンスの新しさ

2026/8/23

利用状況

0 ダウンロード · 0 閲覧

ファイル構成

📁 agents/

📄 openai.yaml

📁 references/

📄 setup.md

📄 sops-notes.md

DevOpsデリバリーを調整

作成者 Brownbull

DevOpsの作業は、パイプライン、インフラストラクチャ、モニタリング、デプロイ判断にまたがることがよくあります。このスキルは、それらのタスクをチェックリスト、引き継ぎ、ロールアウト計画として整理します。

DevOps＆インフラ表示

using-sops

自分のエージェントでインストール

エージェントが読めるリソース

テストする

セキュリティ監査

確認済みのセキュリティ上の懸念 (8)

リスク要因

レポートリンクをコピー

Markdownバッジ

HTMLバッジ

埋め込みカード

APA形式の引用

BibTeX形式の引用

CITATION.cff

Skillstore スコア

作成できるもの

Update Development Configuration

Configure Deployment Secrets

Rotate SOPS Recipients

これらのプロンプトを試す

ベストプラクティス

回避

よくある質問

開発者情報

jssblck のその他のスキル

ship-it

stop-slop

gh-stack

parallel-agents

merge-open-prs

code-craft

関連スキル

incident-command-governor

senior-devops

cloud-devops

terraform-skill

helm-chart-architect

devops-orchestrator