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 Goodsmileduck/claude-registry --skill onepassword-secretsgit clone --depth 1 https://github.com/Goodsmileduck/claude-registryWrote 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/goodsmileduck/claude-registry/onepassword-secrets)<a href="https://agentmods.dev/skills/goodsmileduck/claude-registry/onepassword-secrets"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/onepassword-secrets/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/goodsmileduck/claude-registry/onepassword-secrets"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/onepassword-secrets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00094 | $0.02382 |
| Opus 5 | $0.00047 | $0.01191 |
| Sonnet 5 | $0.00019 | $0.00476 |
| Haiku 4.5 | $0.00009 | $0.00238 |
Grade A, and why
onepassword-secrets scanned grade A with 2 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 600 /dev/shm/config.yml Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **`op run -- <shell|curl|wget|python|node|…>`** is proposed → warn that the child process receives all resolved secrets and can exfiltrate them in the single approved call; ask the user to confirm the child command is How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-cutting rules
These rules apply to every operation in this skill without exception.
- Never print or restate a resolved secret value. If a resolved value appears in output, treat it as compromised and rotate it immediately.
- Reference secrets only as
op://Vault/Item/field(orop://Vault/Item/Section/field). Never embed raw values in code, templates, or responses. - Prefer
op runoverop injectoverop read. Each step down the hierarchy increases the risk that a resolved value reaches context or disk. op item get --revealandop item getwith--format jsonare as dangerous asop read: they print resolved values and must be treated with the same caution.- Always scope with
--vaultto prevent accidental resolution against the wrong vault. - The wrapped child in
op run -- <cmd>is the real risk surface: the child inherits all resolved environment variables. Network tools, shells, and interpreters can exfiltrate those values in a single approved call. - Every
opinvocation requires explicit approval. Never assume a prior approval covers a new call. Never runopspeculatively. Never advise the user to select "always allow" forop.
Setup & auth
The op CLI must be installed, signed in (op signin), and connected to a 1Password account before any secret resolution is possible. Service account authentication uses the OP_SERVICE_ACCOUNT_TOKEN environment variable instead of an interactive session. Biometric unlock requires the desktop app. For installation steps, sign-in flows, and service account configuration, see references/setup-and-auth.md.
Inject secrets
Environment injection (preferred)
Create a .env.tpl file containing only op:// references — no raw values. The template file is safe to commit.
# .env.tpl (safe to commit — contains references, not values)
DB_URL=op://Production/Postgres/connection-string
OPENAI_API_KEY=op://Production/OpenAI/credential
STRIPE_SECRET=op://Production/Stripe/secret_key
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 139 lines · 94 tokens per session scan A 0831c100cd16
onepassword-secrets is a skill published in the GitHub repository Goodsmileduck/claude-registry (1 stars, last pushed 1mo ago), licensed MIT. It adds 94 tokens to every session and 2,382 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
cicd-expert
Expert-level CI/CD with GitHub Actions, Jenkins, deployment pipelines, and automation. Use when the user mentions CI/CD, GitHub Actions, Jenkins, GitLab CI, deployment, or automation, or when the task involves CI/CD Fundamentals, Pipeline Design, Workflow Basics, or Docker Build and Push.
cicd-agent
CI/CD pipeline design and review — GitHub Actions, pipeline best practices, secrets management, deployment strategies, and release automation.
devops-best-practices
Opinionated production-grade DevOps defaults for Terraform, Kubernetes, CI/CD, Docker, cloud security, observability, cost, and disaster recovery. ALWAYS use when generating, reviewing, or modifying any infrastructure code, Kubernetes manifests (Deployment, Service, StatefulSet, Helm, Kustomize), Terraform (.tf…
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.