agent-keybank 0.1.0__tar.gz

agent_keybank-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Jack Ryan
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

agent_keybank-0.1.0/PKG-INFO

@@ -0,0 +1,214 @@
+Metadata-Version: 2.4
+Name: agent-keybank
+Version: 0.1.0
+Summary: Catalog-backed API key loader for coding agents
+Author: Jack Ryan
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/jackaldenryan/agent-keybank
+Project-URL: Repository, https://github.com/jackaldenryan/agent-keybank
+Project-URL: Issues, https://github.com/jackaldenryan/agent-keybank/issues
+Keywords: keybank,api-keys,agents,skills
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Utilities
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# KeyBank
+
+Tell an agent “use the development key.” It matches that phrase to a catalog entry and either writes the key into a `.env` file or sets it for the command it is about to run.
+
+The same skill can add a new API key from a description. The only thing you paste yourself is the secret, into one file: `~/.keybank/secrets.env`.
+
+## Quick start
+
+1. Install the CLI.
+
+```
+pipx install agent-keybank
+```
+
+`uv tool install agent-keybank` works too.
+
+2. Run setup once. It creates `~/.keybank` and asks which coding agents you use, then installs the skill for those agents.
+
+```
+keybank setup
+```
+
+Non-interactive:
+
+```
+keybank setup --agents all
+```
+
+```
+keybank setup --agents claude,codex,cursor
+```
+
+3. Tell an agent what secrets you need. It writes the ids and descriptions. You paste each secret into `~/.keybank/secrets.env`. After that, “use the development key” is enough.
+
+## After install
+
+Say something like: “I need a development key and a production key for my API, both exposed as `SERVICE_API_KEY`.”
+
+The agent adds catalog entries with ids, descriptions, and the runtime name. It does not see the secrets.
+
+Open `~/.keybank/secrets.env` and paste the values yourself:
+
+```
+service-prod=...
+service-dev=...
+```
+
+Do not ask the agent to open that file. Agents must never read it.
+
+From then on you can say:
+
+- “Use the development key and put it in this folder’s `.env`.”
+- “Run this script with the production key.”
+- “Add a staging key that maps to `SERVICE_API_KEY`.”
+
+## Where keys live
+
+The bank is on the machine, not in any git repo. Override the location with `KEYBANK_HOME`.
+
+| File | Who may read it | What it holds |
+| --- | --- | --- |
+| `~/.keybank/catalog.yaml` | You and agents | Id, description, aliases, runtime name, public companions |
+| `~/.keybank/secrets.env` | You and the `keybank` CLI only | The secret for each id |
+
+`catalog.yaml` never contains secrets. `secrets.env` is mode `600` and stores values under the catalog id:
+
+```
+service-prod=...
+service-dev=...
+```
+
+## What setup does
+
+`keybank setup` creates `~/.keybank/` with `catalog.yaml` and `secrets.env` if they are missing, then copies the skill into the agent folders you chose.
+
+`--agents all` covers Claude Code, Codex, Cursor, OpenCode, Gemini, Factory, Grok, and Amp.
+
+Re-run `keybank setup` to refresh the skill. The bank stays put. `pipx upgrade agent-keybank` (or `uv tool upgrade agent-keybank`) refreshes the CLI.
+
+```
+pipx uninstall agent-keybank
+```
+
+Uninstall removes the CLI. It does not delete `~/.keybank`.
+
+## Commands
+
+Discover keys. These print ids and descriptions, never secret values.
+
+```
+keybank list
+```
+
+```
+keybank list --json
+```
+
+```
+keybank show development
+```
+
+```
+keybank resolve "personal project"
+```
+
+Load a key into a folder as the runtime name the process expects.
+
+```
+keybank load development --into ./scripts/my-probe/.env
+```
+
+```
+keybank load service-dev platform-work --into ./scripts/my-probe/.env
+```
+
+```
+keybank load service-dev --as OTHER_API_KEY --into ./scripts/my-probe/.env
+```
+
+`--into DIR` writes `DIR/.env`. `--as VAR` renames the secret for one key.
+
+Run a command with the key in the process environment and skip writing a file.
+
+```
+keybank run development -- python script.py
+```
+
+Add a catalog entry. Then paste the secret into `~/.keybank/secrets.env`. You can also run `keybank set-secret <id>` and type it at a hidden prompt.
+
+```
+keybank add service-dev \
+  --description "Development environment" \
+  --alias dev --alias development \
+  --maps-to SERVICE_API_KEY \
+  --public SERVICE_API_URL=https://api.dev.example.com
+```
+
+Other commands: `keybank init`, `keybank remove <id> --yes`, `keybank doctor`, `keybank home`.
+
+## Catalog format
+
+Agents may read this file. Keep secrets out of it.
+
+```yaml
+keys:
+  - id: service-prod
+    description: Production API, personal project
+    aliases: [prod, production]
+    maps_to: SERVICE_API_KEY
+    public:
+      SERVICE_API_URL: https://api.example.com
+
+  - id: service-dev
+    description: Development environment
+    aliases: [dev, development]
+    maps_to: SERVICE_API_KEY
+    public:
+      SERVICE_API_URL: https://api.dev.example.com
+```
+
+`maps_to` is the environment variable the process should see. That is how two keys both become `SERVICE_API_KEY` at use time. `public` holds non-secret companions such as a base URL.
+
+Prefer letting an agent run `keybank add`. Hand-edits work if you stick to this shape.
+
+## Agent skill
+
+The skill is one file bundled with the CLI. It follows the [Agent Skills](https://agentskills.io) standard. `keybank setup` copies it into the personal skill folders for the agents you pick.
+
+New agent sessions pick it up from those folders. The skill tells the agent to use the CLI and to stay out of secret files.
+
+## Security rules
+
+The CLI is the only process that should open `secrets.env`. It never prints secret values.
+
+Generated `.env` files are mode `600`. Add `.env` to `.gitignore` in the folder you load into.
+
+`keybank run` is the safer option when you do not need a leftover file.
+
+Do not put a master `.env` in a git repo root and do not ask an agent to open it.
+
+## Tests
+
+```
+python3 -m unittest discover -s tests -v
+```
+
+## License
+
+MIT. See [LICENSE](LICENSE). Anyone can use, copy, modify, and distribute this, including commercially.

agent_keybank-0.1.0/README.md

@@ -0,0 +1,189 @@
+# KeyBank
+
+Tell an agent “use the development key.” It matches that phrase to a catalog entry and either writes the key into a `.env` file or sets it for the command it is about to run.
+
+The same skill can add a new API key from a description. The only thing you paste yourself is the secret, into one file: `~/.keybank/secrets.env`.
+
+## Quick start
+
+1. Install the CLI.
+
+```
+pipx install agent-keybank
+```
+
+`uv tool install agent-keybank` works too.
+
+2. Run setup once. It creates `~/.keybank` and asks which coding agents you use, then installs the skill for those agents.
+
+```
+keybank setup
+```
+
+Non-interactive:
+
+```
+keybank setup --agents all
+```
+
+```
+keybank setup --agents claude,codex,cursor
+```
+
+3. Tell an agent what secrets you need. It writes the ids and descriptions. You paste each secret into `~/.keybank/secrets.env`. After that, “use the development key” is enough.
+
+## After install
+
+Say something like: “I need a development key and a production key for my API, both exposed as `SERVICE_API_KEY`.”
+
+The agent adds catalog entries with ids, descriptions, and the runtime name. It does not see the secrets.
+
+Open `~/.keybank/secrets.env` and paste the values yourself:
+
+```
+service-prod=...
+service-dev=...
+```
+
+Do not ask the agent to open that file. Agents must never read it.
+
+From then on you can say:
+
+- “Use the development key and put it in this folder’s `.env`.”
+- “Run this script with the production key.”
+- “Add a staging key that maps to `SERVICE_API_KEY`.”
+
+## Where keys live
+
+The bank is on the machine, not in any git repo. Override the location with `KEYBANK_HOME`.
+
+| File | Who may read it | What it holds |
+| --- | --- | --- |
+| `~/.keybank/catalog.yaml` | You and agents | Id, description, aliases, runtime name, public companions |
+| `~/.keybank/secrets.env` | You and the `keybank` CLI only | The secret for each id |
+
+`catalog.yaml` never contains secrets. `secrets.env` is mode `600` and stores values under the catalog id:
+
+```
+service-prod=...
+service-dev=...
+```
+
+## What setup does
+
+`keybank setup` creates `~/.keybank/` with `catalog.yaml` and `secrets.env` if they are missing, then copies the skill into the agent folders you chose.
+
+`--agents all` covers Claude Code, Codex, Cursor, OpenCode, Gemini, Factory, Grok, and Amp.
+
+Re-run `keybank setup` to refresh the skill. The bank stays put. `pipx upgrade agent-keybank` (or `uv tool upgrade agent-keybank`) refreshes the CLI.
+
+```
+pipx uninstall agent-keybank
+```
+
+Uninstall removes the CLI. It does not delete `~/.keybank`.
+
+## Commands
+
+Discover keys. These print ids and descriptions, never secret values.
+
+```
+keybank list
+```
+
+```
+keybank list --json
+```
+
+```
+keybank show development
+```
+
+```
+keybank resolve "personal project"
+```
+
+Load a key into a folder as the runtime name the process expects.
+
+```
+keybank load development --into ./scripts/my-probe/.env
+```
+
+```
+keybank load service-dev platform-work --into ./scripts/my-probe/.env
+```
+
+```
+keybank load service-dev --as OTHER_API_KEY --into ./scripts/my-probe/.env
+```
+
+`--into DIR` writes `DIR/.env`. `--as VAR` renames the secret for one key.
+
+Run a command with the key in the process environment and skip writing a file.
+
+```
+keybank run development -- python script.py
+```
+
+Add a catalog entry. Then paste the secret into `~/.keybank/secrets.env`. You can also run `keybank set-secret <id>` and type it at a hidden prompt.
+
+```
+keybank add service-dev \
+  --description "Development environment" \
+  --alias dev --alias development \
+  --maps-to SERVICE_API_KEY \
+  --public SERVICE_API_URL=https://api.dev.example.com
+```
+
+Other commands: `keybank init`, `keybank remove <id> --yes`, `keybank doctor`, `keybank home`.
+
+## Catalog format
+
+Agents may read this file. Keep secrets out of it.
+
+```yaml
+keys:
+  - id: service-prod
+    description: Production API, personal project
+    aliases: [prod, production]
+    maps_to: SERVICE_API_KEY
+    public:
+      SERVICE_API_URL: https://api.example.com
+
+  - id: service-dev
+    description: Development environment
+    aliases: [dev, development]
+    maps_to: SERVICE_API_KEY
+    public:
+      SERVICE_API_URL: https://api.dev.example.com
+```
+
+`maps_to` is the environment variable the process should see. That is how two keys both become `SERVICE_API_KEY` at use time. `public` holds non-secret companions such as a base URL.
+
+Prefer letting an agent run `keybank add`. Hand-edits work if you stick to this shape.
+
+## Agent skill
+
+The skill is one file bundled with the CLI. It follows the [Agent Skills](https://agentskills.io) standard. `keybank setup` copies it into the personal skill folders for the agents you pick.
+
+New agent sessions pick it up from those folders. The skill tells the agent to use the CLI and to stay out of secret files.
+
+## Security rules
+
+The CLI is the only process that should open `secrets.env`. It never prints secret values.
+
+Generated `.env` files are mode `600`. Add `.env` to `.gitignore` in the folder you load into.
+
+`keybank run` is the safer option when you do not need a leftover file.
+
+Do not put a master `.env` in a git repo root and do not ask an agent to open it.
+
+## Tests
+
+```
+python3 -m unittest discover -s tests -v
+```
+
+## License
+
+MIT. See [LICENSE](LICENSE). Anyone can use, copy, modify, and distribute this, including commercially.

agent_keybank-0.1.0/agent_keybank.egg-info/PKG-INFO

@@ -0,0 +1,214 @@
+Metadata-Version: 2.4
+Name: agent-keybank
+Version: 0.1.0
+Summary: Catalog-backed API key loader for coding agents
+Author: Jack Ryan
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/jackaldenryan/agent-keybank
+Project-URL: Repository, https://github.com/jackaldenryan/agent-keybank
+Project-URL: Issues, https://github.com/jackaldenryan/agent-keybank/issues
+Keywords: keybank,api-keys,agents,skills
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Utilities
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# KeyBank
+
+Tell an agent “use the development key.” It matches that phrase to a catalog entry and either writes the key into a `.env` file or sets it for the command it is about to run.
+
+The same skill can add a new API key from a description. The only thing you paste yourself is the secret, into one file: `~/.keybank/secrets.env`.
+
+## Quick start
+
+1. Install the CLI.
+
+```
+pipx install agent-keybank
+```
+
+`uv tool install agent-keybank` works too.
+
+2. Run setup once. It creates `~/.keybank` and asks which coding agents you use, then installs the skill for those agents.
+
+```
+keybank setup
+```
+
+Non-interactive:
+
+```
+keybank setup --agents all
+```
+
+```
+keybank setup --agents claude,codex,cursor
+```
+
+3. Tell an agent what secrets you need. It writes the ids and descriptions. You paste each secret into `~/.keybank/secrets.env`. After that, “use the development key” is enough.
+
+## After install
+
+Say something like: “I need a development key and a production key for my API, both exposed as `SERVICE_API_KEY`.”
+
+The agent adds catalog entries with ids, descriptions, and the runtime name. It does not see the secrets.
+
+Open `~/.keybank/secrets.env` and paste the values yourself:
+
+```
+service-prod=...
+service-dev=...
+```
+
+Do not ask the agent to open that file. Agents must never read it.
+
+From then on you can say:
+
+- “Use the development key and put it in this folder’s `.env`.”
+- “Run this script with the production key.”
+- “Add a staging key that maps to `SERVICE_API_KEY`.”
+
+## Where keys live
+
+The bank is on the machine, not in any git repo. Override the location with `KEYBANK_HOME`.
+
+| File | Who may read it | What it holds |
+| --- | --- | --- |
+| `~/.keybank/catalog.yaml` | You and agents | Id, description, aliases, runtime name, public companions |
+| `~/.keybank/secrets.env` | You and the `keybank` CLI only | The secret for each id |
+
+`catalog.yaml` never contains secrets. `secrets.env` is mode `600` and stores values under the catalog id:
+
+```
+service-prod=...
+service-dev=...
+```
+
+## What setup does
+
+`keybank setup` creates `~/.keybank/` with `catalog.yaml` and `secrets.env` if they are missing, then copies the skill into the agent folders you chose.
+
+`--agents all` covers Claude Code, Codex, Cursor, OpenCode, Gemini, Factory, Grok, and Amp.
+
+Re-run `keybank setup` to refresh the skill. The bank stays put. `pipx upgrade agent-keybank` (or `uv tool upgrade agent-keybank`) refreshes the CLI.
+
+```
+pipx uninstall agent-keybank
+```
+
+Uninstall removes the CLI. It does not delete `~/.keybank`.
+
+## Commands
+
+Discover keys. These print ids and descriptions, never secret values.
+
+```
+keybank list
+```
+
+```
+keybank list --json
+```
+
+```
+keybank show development
+```
+
+```
+keybank resolve "personal project"
+```
+
+Load a key into a folder as the runtime name the process expects.
+
+```
+keybank load development --into ./scripts/my-probe/.env
+```
+
+```
+keybank load service-dev platform-work --into ./scripts/my-probe/.env
+```
+
+```
+keybank load service-dev --as OTHER_API_KEY --into ./scripts/my-probe/.env
+```
+
+`--into DIR` writes `DIR/.env`. `--as VAR` renames the secret for one key.
+
+Run a command with the key in the process environment and skip writing a file.
+
+```
+keybank run development -- python script.py
+```
+
+Add a catalog entry. Then paste the secret into `~/.keybank/secrets.env`. You can also run `keybank set-secret <id>` and type it at a hidden prompt.
+
+```
+keybank add service-dev \
+  --description "Development environment" \
+  --alias dev --alias development \
+  --maps-to SERVICE_API_KEY \
+  --public SERVICE_API_URL=https://api.dev.example.com
+```
+
+Other commands: `keybank init`, `keybank remove <id> --yes`, `keybank doctor`, `keybank home`.
+
+## Catalog format
+
+Agents may read this file. Keep secrets out of it.
+
+```yaml
+keys:
+  - id: service-prod
+    description: Production API, personal project
+    aliases: [prod, production]
+    maps_to: SERVICE_API_KEY
+    public:
+      SERVICE_API_URL: https://api.example.com
+
+  - id: service-dev
+    description: Development environment
+    aliases: [dev, development]
+    maps_to: SERVICE_API_KEY
+    public:
+      SERVICE_API_URL: https://api.dev.example.com
+```
+
+`maps_to` is the environment variable the process should see. That is how two keys both become `SERVICE_API_KEY` at use time. `public` holds non-secret companions such as a base URL.
+
+Prefer letting an agent run `keybank add`. Hand-edits work if you stick to this shape.
+
+## Agent skill
+
+The skill is one file bundled with the CLI. It follows the [Agent Skills](https://agentskills.io) standard. `keybank setup` copies it into the personal skill folders for the agents you pick.
+
+New agent sessions pick it up from those folders. The skill tells the agent to use the CLI and to stay out of secret files.
+
+## Security rules
+
+The CLI is the only process that should open `secrets.env`. It never prints secret values.
+
+Generated `.env` files are mode `600`. Add `.env` to `.gitignore` in the folder you load into.
+
+`keybank run` is the safer option when you do not need a leftover file.
+
+Do not put a master `.env` in a git repo root and do not ask an agent to open it.
+
+## Tests
+
+```
+python3 -m unittest discover -s tests -v
+```
+
+## License
+
+MIT. See [LICENSE](LICENSE). Anyone can use, copy, modify, and distribute this, including commercially.

agent_keybank-0.1.0/agent_keybank.egg-info/SOURCES.txt

@@ -0,0 +1,13 @@
+LICENSE
+README.md
+pyproject.toml
+agent_keybank.egg-info/PKG-INFO
+agent_keybank.egg-info/SOURCES.txt
+agent_keybank.egg-info/dependency_links.txt
+agent_keybank.egg-info/entry_points.txt
+agent_keybank.egg-info/top_level.txt
+keybank/__init__.py
+keybank/__main__.py
+keybank/cli.py
+keybank/skill/SKILL.md
+tests/test_keybank.py

agent_keybank-0.1.0/agent_keybank.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

agent_keybank-0.1.0/agent_keybank.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+keybank = keybank.cli:main

agent_keybank-0.1.0/agent_keybank.egg-info/top_level.txt

@@ -0,0 +1 @@
+keybank

agent_keybank-0.1.0/keybank/__init__.py

@@ -0,0 +1,2 @@
+from keybank.cli import *  # noqa: F403
+from keybank.cli import __version__, main

agent_keybank-0.1.0/keybank/__main__.py

@@ -0,0 +1,3 @@
+from keybank.cli import main
+
+raise SystemExit(main())