Densom Claude 1password
- 7 repo stars
- Updated October 29, 2025
- densom/claude-1password
densom-claude-1password is a Claude Code plugin that helps populate and manage local .env files from 1Password secrets.
About
The densom-claude-1password Claude Code plugin marketplace offers tooling to manage local.env files using 1Password secrets—a common pain point for developers who juggle many API keys across side projects. Instead of storing credentials in notes or committing example env files with real values, you register the plugin and use its skills to pull from 1Password into dotenv files on your machine during build-time integration work. It is phase-specific to build integrations: you are not running production monitoring or launch SEO with it, but you are making Claude-assisted coding safer and faster when every new service needs STRIPE_, OPENAI_, or database URLs. Beginner-friendly assuming you already use 1Password CLI or equivalent local auth. This is a secrets-focused dev plugin bundle, not a full vault auditor or CI secret injector—optimize for day-one local setup before security hardening.
- Plugin collection focused on local .env management via 1Password
- Targets local-development workflows without committing secrets to git
- Keywords cover dotenv, populate, and secrets management tooling
- Fits densom development-category marketplace entry with 1 plugin
- Reduces manual copy-paste of vault items into environment files
Densom Claude 1password by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install densom-claude-1password@densom/claude-1passwordAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 7 |
|---|---|
| Last updated | October 29, 2025 |
| Repository | densom/claude-1password ↗ |
What it does
Populate and manage local.env files from 1Password secrets so Claude Code workflows never paste production keys into chat.
Who is it for?
Claude Code users on macOS or Linux who already store dev secrets in 1Password and want agent-assisted dotenv setup.
Skip if: Skip if you need centralized CI/CD secret injection, production KMS rotation, or compliance audits without local 1Password.
What you get
After you add the plugin, you can hydrate local environment files from 1Password-backed secrets while keeping credentials out of chat and git.
- Locally populated .env (or env.*) files sourced from 1Password items
- Repeatable secret sync workflow for new integrations without manual paste
By the numbers
- Marketplace lists 1 plugin in the collection
- Repository description specifies managing local .env files using 1Password secrets
Recommended Plugins
1mangesh1 Hipaa GuardianAI agent skill for HIPAA compliance - PHI/PII detection, code scanning, audit reports, and remediation guidance6
Abossenbroek Abossenbroek Claude PluginsCustom Claude Code plugins by abossenbroek2
Agentsecops SecopsagentkitSecurity operations toolkit for AI coding agents.181
Agent Sh EnhancePlugin structure and tool use analyzer - validates plugin.json, MCP tools, and security patterns3
Altic Dev EnvaultLet agents safely manage env variables6
Auth0 Agent SkillsAuth0 Agent Skills40How it compares
Local 1Password-to-dotenv helper plugin, not a broad MCP server catalog or application security scanner.
FAQ
Who is Densom Claude 1password for?
It is for developers using Claude Code locally who keep secrets in 1Password and want safer.env file management.
When should I use Densom Claude 1password?
Use it when starting or updating a project integration and you need to populate.env from vault items without pasting secrets into the agent.
How do I add Densom Claude 1password to my agent?
Install the densom/claude-1password marketplace plugin in Claude Code, sign in to 1Password CLI locally, then run the plugin skills to sync secrets into your env files.