Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add lxb12123/prompt-pocket --skill usuallygit clone --depth 1 https://github.com/lxb12123/prompt-pocketWrote 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.
[](https://agentmods.dev/skills/lxb12123/prompt-pocket/usually)<a href="https://agentmods.dev/skills/lxb12123/prompt-pocket/usually"><img src="https://agentmods.dev/badge/skills/lxb12123/prompt-pocket/usually/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.
<a href="https://agentmods.dev/skills/lxb12123/prompt-pocket/usually"><img src="https://agentmods.dev/badge/skills/lxb12123/prompt-pocket/usually.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00130 | $0.01949 |
| Opus 5 | $0.00065 | $0.00975 |
| Sonnet 5 | $0.00026 | $0.00390 |
| Haiku 4.5 | $0.00013 | $0.00195 |
Grade A, and why
usually 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 10d ago.
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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/usually — Prompt Pocket
Remember your most-used prompts, manage them in one place, and pick one to run. All data and frequency counting are done by a deterministic script (0 tokens); your only job is: decide the sub-action → call the script → let the user pick from a menu → run the picked prompt.
The script (run this; it prints a single JSON object — just relay it)
The deterministic core is pocket.mjs. Resolve its path once, then reuse it:
- Preferred:
~/.prompt-pocket/pocket.mjs(absolute — works on every host and from any directory, including global / plugin installs). - In this repo:
skills/usually/scripts/pocket.mjsalso works. - Bootstrap (do this if
~/.prompt-pocket/pocket.mjsis missing and you can see the repo copy):mkdir -p ~/.prompt-pocket && cp skills/usually/scripts/pocket.mjs ~/.prompt-pocket/pocket.mjs - Keep it fresh: if you can see the repo copy, refresh the runtime copy so the native
dropdown feature is present:
cp skills/usually/scripts/pocket.mjs ~/.prompt-pocket/pocket.mjs
Below, POCKET means whichever path exists — e.g. run node ~/.prompt-pocket/pocket.mjs <command>.
Store lives at ~/.prompt-pocket/store.json (user-level, shared across agents:
Claude / Codex / OpenCode read the same pocket).
scan reads Claude (~/.claude/projects), Codex (~/.codex/sessions) and OpenCode
(~/.local/share/opencode/opencode.db) session history.
First, decide which sub-action the user wants
From what the user said this turn (could be /usually, /usually add ..., or natural
language) pick one:
| User intent | Sub-action |
|---|---|
just /usually, "list my usual prompts", "what do I usually say", "列一下我常用的" |
list + pick to run (main flow, below) |
| "save this", "add this one", "remember this for later" | add |
| "delete that one", "remove …", "delete" | delete |
| "change that one", "rename … to …", "edit" | edit |
| "is there a … one", "find …", "did I say … before" | find |
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.
- 10d ago First seen · 148 lines · 130 tokens per session scan A 6961e68b9f38
usually is a skill published in the GitHub repository lxb12123/prompt-pocket (4 stars, last pushed 2mo ago), licensed MIT. It adds 130 tokens to every session and 1,949 once invoked, about $0.0006 per session on Opus 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.
Other skills, from other repositories
community
Use when building or running a persistent two-way community space — Discord, Telegram, Circle: platform choice, structure, onboarding, native→bot→human moderation, rituals, growth loops, health metrics. NOT churn of paying product customers (that is retention), NOT broadcast email (that is newsletter), NOT one live…
parallel
Use when two or more pieces of work are genuinely independent — disjoint files, no shared state, no ordering edge — and should fan out across subagents, then be gathered and reconciled under a combined test suite. Decides WHAT can run concurrently; NOT the isolation it runs in (that is worktrees), NOT the per-unit TDD…
orient
Always-on. The brújula: close every turn by situating the person — where they are, what just happened, why it mattered, and the next step as a question, never a dead end. Reads the accompaniment and technical dials from 02-DOCS and calibrates how much it explains, rewriting the dial when the user asks for more or…
neosh
Run and manage long-lived coding agents in a neosh workspace from the command line — start conversations in any directory or git worktree, fan work out across many at once, watch and steer them while they run, read what they produced, and clean up. Use whenever the user asks to delegate work to neosh, run something…
task-creator
Guide and schema for creating reusable saved tasks. Use whenever creating, saving, or defining an automated task.
google-workspace
Gmail, Calendar, Drive, Contacts, Sheets, and Docs integration via Python. Uses OAuth2 with automatic token refresh. No external binaries needed — runs entirely with Google's Python client libraries in the Hermes venv.