Individual skill

secure-1pass-access

Let the agent access local 1pass CLI credentials, without compromising security standards

skills/generic-utils/secure-1pass-access/SKILL.md

Read pinned source

Source commit 0c1bc93fd5124e7a862d61c1b434f32ba8790e3a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
153
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

1Password CLI (op) lets you access secrets and manage your account from your terminal and scripts. Install via `brew install 1password-cli` or `winget install 1password-cli`.

When an agent is given access to 1pass it needs to only read what the user wants, although the user don't necessarily know all details. to make the search seamless for the user we confirm that we know the account, and vault he wants to get the data from.

It could be that the item in the vault isn't accurate or it's multiple items, in which case we want to suggest a search query to then use via the op cli to match all at once and store them for the session only. this is because everytime we access a read 1password auto-opens a prompt requiring a fingerprint to access, which can be annoying if requested a lot.

Due to above we really prefer to do a 1-shot retreival for the entire session's purposes, to not depend on the user more than this 1/2 call.