Yesterday a developer shipped a Prompt Vault plugin for Hermes Agent. On the surface: a clean prompt library with tags, version history, and favorites. Useful. But step 2 is the actual twist. You can call any saved prompt from Telegram, Discord, Slack, or a terminal. Same vault. Everywhere you already work. Think about what that actually means. You are mid-conversation in Slack, someone asks you to review their copy, and instead of opening three browser tabs to find that prompt you wrote six weeks ago, you type one command and it drops straight into your workflow. No tab switching. No rewriting from memory. No “I know I had a better version of this somewhere.” No cloud sync. No third-party storage. SQLite lives on your machine, nothing leaves it. That last part matters more than people are giving it credit for. Most prompt libraries today either live in some SaaS tool that owns your data, or they are buried in Notion pages behind three levels of nesting. This keeps everything local and portable. If you move machines, you copy one file. If the service shuts down, you lose nothing. That is a genuinely different design philosophy, and it shows. One person in the comments said it perfectly: they kept rewriting prompts they already had because everything was scattered across Notion, random docs, and chat history. That is most of us. You spend 20 minutes crafting a prompt that finally gets the output right, use it once, then can never locate it again when you need it two weeks later. The loss is invisible but real. It compounds across every project, every client, every deadline.
How the workflow actually looks:
- 🔍
/vault search code review, find what you need in seconds. The search is fuzzy, so you do not need to remember the exact title. Type a keyword, get a ranked list, pick the one that fits. - 📋
/vault use a1b2c3d4, grab the prompt and drop it into your flow. The ID is short enough to type from memory after a few uses. The most-used ones stick fast. - 💾
/vault save Title | content, capture a winner the moment it works. This is the habit that makes the whole system pay off. You do not archive prompts after the fact. You save them while the context is fresh, right when you know exactly why this version worked where the others did not. Treat it like committing code: save often, save with intention. - 📊
/vault stats, see which prompts you actually reach for. This is where the system starts teaching you things. You will find prompts you thought were occasional use are actually central to your workflow. You will also find favorites collecting dust, which tells you something has shifted in how you work or what you are building.
Pro tip: Tag by use case, not by tool
“email-subject-line” beats “Claude prompts.” When you are searching at 11pm, you will thank yourself. The tool you are running the prompt through is irrelevant at search time. What you need to remember is the job: what problem were you solving, what type of output were you after. Tag for the problem, not the solution. Go one level deeper: use compound tags. “newsletter-hook-curiosity” or “ad-copy-objection-handling” will save you more time than single-word tags ever will. A little extra friction at save time removes a lot of friction at use time.
Pro tip 2: Version history is underrated
When a prompt starts underperforming after a model update, you can roll back and compare what changed. That is real debugging leverage. Models shift behavior with every update, sometimes subtly. A prompt that was producing sharp, concise outputs in January might start returning bloated paragraphs in March with zero changes on your end. Version history turns that from a mystery into a traceable diff. This is also useful when you are iterating on a prompt deliberately. Keep saving new versions as you improve. When you find the version that works best, you have a clear record of what changed and why. That record is worth something next time you build a prompt from scratch in the same category. A good prompt library compounds. What you save in month one is worth 10x in month six. Not because the prompts get better on their own, but because you stop recreating work you already did. Every saved prompt is time you do not spend thinking up the same solution twice. At scale, that is a real productivity edge, not a marginal one. Plugin is open source and free: github.com/LeventeNagy/hermes-prompt-vault 🚀
Frequently Asked Questions
Q: What problem does this solve?
Sound familiar? Prompts scattered across Notion, random docs, chat history. Then you don’t remember what you already built and end up recreating the same thing twice. The Prompt Vault puts everything in one searchable database so you can instantly find and reuse what you’ve already got.
Q: Can I import my existing prompts from Notion or other tools?
Yep , the plugin supports import/export, so you can bring your existing prompts in. Once imported, they’re searchable and accessible from CLI, Telegram, Discord, Slack, or Terminal. Tags and categories keep everything organized.
Q: Is this really private, and does it sync across devices?
Everything stays local in SQLite on your machine , nothing goes to the cloud, so privacy is solid. The tradeoff is that syncing across devices isn’t built-in. If you need multi-device access, you’d need to export/import or use cloud storage separately.
Q: How does search keep me from rebuilding prompts I already have?
Commands like /vault search code review instantly pull up everything related. Tagging makes discovery faster. Before you write a new prompt, a quick search shows what’s already in your vault. Saves time, keeps your library from becoming a graveyard.
I built a Prompt Vault plugin for Hermes Agent — save, search, and reuse prompts from any platform
by u/JealousPlastic in PromptEngineering