psamvault-mcp: Instructions file for Codex

AGENTS.md

psamvault-mcp AGENTS.md is an instructions file for Codex, OpenCode from psam-717/psamvault-mcp. It costs 2,629 tokens per session, scanned A, original, MIT.

Repository instructions for psamvault-mcp, an MCP server that manages credentials while keeping secret values out of the agent's context. They also describe available prompt templates and installation steps.

In plain words
What is it for?
Use them when installing psamvault-mcp, troubleshooting its connection, retrieving guidance prompts, or working with managed credentials.
Why use it?
They give the agent safe, specific guidance for connecting to and using the credential manager instead of guessing at setup commands.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is psam-717/psamvault-mcp's own configuration. It tells Codex and OpenCode how to work on psamvault-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything psamvault-mcp configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/user/my-project.

Reuse

Borrowing it

Nothing to install: this file belongs to psam-717/psamvault-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/psam-717/psamvault-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/psam-717/psamvault-mcp

Made for: Codex, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for psamvault-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/psam-717/psamvault-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/psam-717/psamvault-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/psam-717/psamvault-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/psam-717/psamvault-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for psamvault-mcp AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/psam-717/psamvault-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/psam-717/psamvault-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,629 This file is loaded in full into every session.
When invoked 2,629 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.02629 $0.02629
Opus 5.5 $0.01052 $0.01052
Sonnet 5.5 $0.00526 $0.00526
Haiku 4.5 $0.00263 $0.00263

Measured today against content hash 706b9d2787e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

psamvault-mcp AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

AGENTS.md · 170 lines

How it starts

The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.

psamvault-mcp — Agent Instructions

You have the psamvault MCP server available. It provides credential management tools that keep secrets out of your context window.

Prompt templates are available via the MCP Prompts capability (list_prompts / get_prompt) — load these at runtime for detailed step-by-step guidance on each workflow.

If the MCP server is NOT connected yet

Do not improvise with pip install into system Python or bare psamvault get. Follow this playbook:

Full guide: docs/troubleshooting/MCP-INSTALL-AND-CONNECT.md

Short install playbook

  1. Install with pipx only: pipx install psamvault-mcp
  2. If pipx reports missing metadata or uninstall fails, delete the broken venv. Ask pipx where it is: pipx environment --value PIPX_LOCAL_VENVS (current pipx: ~/.local/share/pipx/venvs on Linux, ~/Library/Application Support/pipx/venvs on macOS, %LOCALAPPDATA%\pipx\pipx\venvs on Windows). Then reinstall.
  3. Resolve the absolute path to the pipx binary (~/.local/bin/psamvault-mcp or %USERPROFILE%\.local\bin\psamvault-mcp.exe). If PATH has multiple copies, ignore system Python3xx\Scripts\ shims — they often lack deps (ModuleNotFoundError: pydantic).
  4. Write host config with that absolute path and env: { PYTHONPATH: "" } (avoids Hermes/global PYTHONPATH contamination). On Linux the server adopts /run/user/<uid>/bus when that socket belongs to this user; if it is not visible, also pass DBUS_SESSION_BUS_ADDRESS. macOS and Windows need no extra variable. See OS keyring.
  5. Reload the host (restart session / refresh MCP). Mid-session config edits often do not expose tools until reload.
  6. Smoke-test the binary with psamvault-mcp --version or psamvault-mcp --help (safe — print and exit). Do not leave a bare psamvault-mcp process running in a shell — it waits on stdio for MCP.
  7. Ask the user to run psamvault login if vault tools report session timeout / not logged in.
  8. Verify: get_version → list_vault_sites.

Read the full file on GitHub · 170 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. today Changed · +226 tokens per session 706b9d2787e1
  2. 9d ago Changed · +156 tokens per session f430794fdafb
  3. 29d ago Changed · +1 lines · +14 tokens per session 560cd3be1473
  4. 1mo ago Changed · +14 lines · +211 tokens per session 8c0e8aec44dc
  5. 1mo ago Changed · +1 lines · +39 tokens per session c94e3b8d0432
  6. 1mo ago Changed · +10 lines · +207 tokens per session d60ce34ff64d
  7. 1mo ago Changed · +3 lines · +81 tokens per session a6ff16039752
  8. 1mo ago First seen · 141 lines · 1,695 tokens per session scan A f18321582084

Subscribe to this mod's changes

psamvault-mcp AGENTS.md is an instructions file published in the GitHub repository psam-717/psamvault-mcp (2 stars, last pushed today), licensed MIT. It adds 2,629 tokens to every session, about $0.0105 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other instructions, from other repositories