password-manager
Skill5 starsChanged 8 months agoMITView on GitHub
Access 1Password secrets and inject environment variables via the op CLI. Use when user needs to retrieve credentials, inject secrets into commands, or look up stored items. Never stores or logs secrets.
- Reads credentials
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- rakaarwaky/agents-arwakytheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- rakaarwaky/agents-arwaky★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- apple-notesSkill
- apple-remindersSkill
- bear-notesSkill
- brainstormSkill
- cameraSkill
- content-creatorSkill
- context-healthSkill
- daily-briefingSkill
- deep-readSkill
- draft-messageSkill
- emailSkill
- exa-searchSkill
- gh-issuesSkill
- gif-searchSkill
- github-opsSkill
- google-workspaceSkill
- hue-lightsSkill
- image-genSkill
- imessageSkill
- memory-managerSkill
- migrate-openclawSkill
- notionSkill
- obsidianSkill
- pdf-editorSkill
- peekabooSkill
- placesSkill
- podcast-makerSkill
- quick-researchSkill
- rss-monitorSkill
- security-auditSkill
- session-logsSkill
- setupSkill
- skill-creatorSkill
- slack-opsSkill
- smart-bedSkill
- sonosSkill
- speech-to-textSkill
- spotifySkill
- summarizeSkill
- task-trackerSkill
- text-to-speechSkill
- things-macSkill
- tmux-controlSkill
- trelloSkill
- trend-scoutSkill
- video-extractSkill
- weatherSkill
- whatsappSkill
- x-twitterSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 21
Read secrets and inject environment variables from 1Password using the op CLI.
- Very specific: line 82
Always check if CLI is installed and signed in: op whoami
- Very specific: line 83
If not installed, show brew install 1password-cli and stop
- Very specific: line 84
If not signed in, show op signin and stop
- Distinctive: line 85
NEVER print secret values in assistant responses — only confirm "retrieved" or use them directly in commands
- Very specific: line 86
NEVER write secrets to files that might be committed (e.g., .env in a git repo) without warning the user
- Distinctive: line 87
NEVER log, store, or repeat credential values in memory or workspace files
- Very specific: line 88
Use op read URI format for precise field access.
- Distinctive: line 90
If the user asks "what's my password for X", retrieve it and only show the value in the terminal — do not include it in any saved file
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Password Manager (1Password)
Read secrets and inject environment variables from 1Password using the op CLI.
Prerequisites
brew install 1password-cliSign in:
op signinOr for biometric unlock (recommended):
- Open 1Password app → Settings → Developer → enable "Integrate with 1Password CLI"
- Then
opcommands will use Touch ID automatically
Verify:
op whoamiCommands
| Command | Description |
op whoami | Show current signed-in account |
op vault list | List all vaults |
op item list | List all items |
op item list --vault "<Vault>" | List items in a vault |
op item get "<Item Name>" | Get full item details |
op item get "<Item Name>" --fields password | Get just the password field |
op read "op://<vault>/<item>/<field>" | Read a specific field by URI |
op run --env-file=.env.1p -- <command> | Inject secrets as env vars and run command |
op inject -i .env.tpl -o .env | Render a secrets template to a file |
Usage Examples
Get an API key:
op read "op://Personal/OpenAI/api_key"Get a database password:
op item get "Production DB" --fields passwordInject secrets and run a script:
# .env.1p file contains: API_KEY=op://Work/MyService/api_key
op run --env-file=.env.1p -- python3 script.pyList all items in Work vault:
op item list --vault "Work" --format json | jq '.[].title'Rules
- Always check if CLI is installed and signed in:
op whoami - If not installed, show
brew install 1password-cliand stop - If not signed in, show
op signinand stop - NEVER print secret values in assistant responses — only confirm "retrieved" or use them directly in commands
- NEVER write secrets to files that might be committed (e.g.,
.envin a git repo) without warning the user - NEVER log, store, or repeat credential values in memory or workspace files
- Use
op readURI format for precise field access; useop item getwhen unsure of field names - For injecting into commands, prefer
op runover reading the secret and passing it as an argument - If the user asks "what's my password for X", retrieve it and only show the value in the terminal — do not include it in any saved file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

