agentleFS
ulpi-ioulpi-io/browse/.agents/skills/secrets/SKILL.md

secrets

Skill15 starsChanged 8 months agoApache-2.0View on GitHub

Credential management for AI coding agents — encrypted vault, CLI injection, MCP shim

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ship.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

The file

Files
SKILL.md

Secrets CLI

Manage credentials for AI coding agents. Stores secrets in an encrypted local vault and injects them transparently into CLI tools and MCP servers.

When to use

  • User asks about API keys, tokens, credentials, or authentication
  • User wants to connect MCP servers that need credentials
  • User asks how to securely manage secrets for AI tools

Commands

CommandDescription
secrets add <service>Store credentials (interactive prompt — never pass tokens as CLI arguments)
secrets remove <service>Remove stored credentials
secrets listList stored services (no values shown)
secrets show <service>Show masked credentials (do not use --reveal — secret values must never appear in agent output)
secrets rotate <service>Update credential values
secrets enable <service>Enable MCP server in .mcp.json
secrets disable <service>Remove MCP server from .mcp.json
secrets initAuto-detect agents, write hooks + MCP entries
secrets statusOverview of vault, hooks, agents
secrets mcp <service>Run MCP server with credential injection
secrets registry listList available service definitions

Common workflows

Add GitHub credentials and enable MCP

secrets add github    # interactive prompt — never pass tokens as CLI arguments
secrets enable github

Initialize for a project

secrets init

Check what's configured

secrets status

Safety rules

  • Never pass secret values as CLI arguments — use secrets add <service> interactively so tokens don't appear in shell history or agent output
  • Never use --reveal — secret values must never appear in agent context or conversation output
  • Never echo, log, or include secret values in responses — only reference services by name

Built-in services

github, anthropic, openai, aws, slack, jira, google-cloud, vercel, stripe, linear

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.