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.
npx skills add joaquimscosta/arkhe-claude-plugins --skill sops-decryptgit clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/sops-decrypt)<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/sops-decrypt"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/sops-decrypt/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/sops-decrypt"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/sops-decrypt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 4 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 47 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 6 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 45 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00069 | $0.00639 |
| Opus 5 | $0.00034 | $0.00319 |
| Sonnet 5 | $0.00014 | $0.00128 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
sops-decrypt 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 9d ago.
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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOPS Decrypt
Decrypt .enc.yaml files back to their plaintext .env originals.
Workflow
-
Detect current state:
python3 ${CLAUDE_SKILL_DIR}/../sops-setup/scripts/detect_sops.py <project-root> -
Verify prerequisites:
tools.sops.installedmust be true — if not, tell user to install:brew install sops(macOS) or download binary (Linux)age_key.existsmust be true — if not, guide user to place their age private key at the expected path, or setSOPS_AGE_KEY_FILEenv var
-
Show encrypted files from
project.encrypted_files. If empty, report "No encrypted files found" and exit. -
Use
AskUserQuestion(multiSelect: true) — which files to decrypt. For each, show the target output name (e.g.,.env.local.enc.yaml→.env.local). If the target file already exists, note it will be overwritten. -
Decrypt each selected file (decrypt YAML, then convert to dotenv):
sops --decrypt <file>.enc.yaml > <file>.dec.yaml.tmp python3 ${CLAUDE_SKILL_DIR}/../sops-setup/scripts/dotenv_yaml.py to-dotenv <file>.dec.yaml.tmp > <target-env-file> rm <file>.dec.yaml.tmpWhere
<target-env-file>is the encrypted filename with.enc.yamlsuffix removed. Example:.env.local.enc.yaml→.env.local -
Verify each decrypted file exists and is non-empty.
-
Summary:
| Encrypted File | Decrypted To | Status | |---------------|--------------|--------| | .env.local.enc.yaml | .env.local | done |Remind user: Do NOT commit the decrypted .env files — they should be in
.gitignore.
Key Rules
- Always check that the age private key exists before attempting decryption
- Always convert YAML→dotenv after decrypting (use the helper script)
- Warn if a decrypted file will overwrite an existing one
- Clean up
.tmpfiles even if decryption fails - After decryption, remind user that plaintext
.envfiles must stay out of git - If decryption fails with "no identity matched", the machine's key is not authorized — suggest running
/devtools:sops-add-keyon a machine that has access
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.
- 9d ago First seen · 57 lines · 69 tokens per session scan A 36e16e3d6ec8
sops-decrypt is a skill published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed 26d ago), licensed MIT. It adds 69 tokens to every session and 639 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
skill-capture
Turn a recurring in-session workflow into a reusable Claude Code skill. Load this the moment you notice you have run the SAME multi-step sequence (same ordered steps or commands, small variation allowed) about three times in the current session, or when open candidates are waiting in .credo/skill-candidates.md at…
test-writer
Generate comprehensive tests including unit, integration, and property-based tests.
quick
Fast path — skip the full workflow for small tasks under 3 files.
git-workflow
Git branching, commits, and PR workflow following GitFlow conventions.
refactor-planner
Plan safe refactoring with dependency analysis, impact assessment, and rollback strategies.
cross-cutting-checklist-generator
Detect when a concern is scattered across many places in a project (config keys, enums, translations, feature flags, API endpoints, doc references) and auto-generate a project-local checklist so that same concern is never partially updated again. Use whenever you add or change something that also exists in several…