pocket: Instructions file for Claude Code

AGENTS.md

pocket AGENTS.md is an instructions file for Claude Code, Codex, OpenCode from filopedraz/pocket. It costs 1,880 tokens per session, scanned A, original, MIT.

Instructions for Pocket, a portable memory store for command-line coding agents. It keeps durable notes and past conversations in a shared folder so different agents can use the same context.

In plain words
What is it for?
Use it at the start of an agent session to read durable preferences, or use its command-line tool to initialize memory, find past conversations, and review recent sessions.
Why use it?
It prevents useful project and user context from being lost when switching between AI providers or command-line tools. It also sets rules for reading memory and searching old chats without loading everything.

Instructions file for Claude CodeCodexOpenCode

Written for Claude Code and Codex and OpenCode: UserPromptSubmit hook event, but also the file is AGENTS.md. Also seen: mentions subagents; mentions Claude Code; mentions AGENTS.md.

This is filopedraz/pocket's own configuration. It tells Claude Code, Codex and OpenCode how to work on pocket 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 pocket configures →

Reuse

Borrowing it

Nothing to install: this file belongs to filopedraz/pocket. 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/filopedraz/pocket/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/filopedraz/pocket

Made for: Claude Code, 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 pocket AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/filopedraz/pocket/agents-md/github.svg)](https://agentmods.dev/instructions/filopedraz/pocket/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/filopedraz/pocket/agents-md"><img src="https://agentmods.dev/badge/instructions/filopedraz/pocket/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 pocket AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/filopedraz/pocket/agents-md"><img src="https://agentmods.dev/badge/instructions/filopedraz/pocket/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,880 This file is loaded in full into every session.
When invoked 1,880 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.01880 $0.01880
Opus 5.5 $0.00752 $0.00752
Sonnet 5.5 $0.00376 $0.00376
Haiku 4.5 $0.00188 $0.00188

Measured 2mo ago against content hash eafc1a09942e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pocket 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 2mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 187 lines

How it starts

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

AGENTS.md

Notes for any AI agent (Claude Code, Codex, OpenCode, …) running inside this repo.

What this repo is

A pocket — a portable memory store for CLI agents. The whole point: you read durable knowledge from memory/general.md at the start of every session, and you can recall past conversations from chats/ regardless of which agent originally produced them.

If the human runs out of credits on one provider, they switch CLIs. The folder layout doesn't move. The context is still here.

What to do at session start

  1. Read memory/general.md. That's who the human is and how they want to be talked to. Ground every response in it. If the file is missing, run bin/pocket init first.

  2. Don't auto-ingest chats/. It can be large. Pull from it on demand via bin/pocket when a topic from a past conversation is relevant.

The pocket CLI

The bin/pocket shim runs a small TypeScript CLI in cli/ (Bun + Biome). It is the only thing you should use to read chats/ or scaffold local files.

bin/pocket init               scaffold memory/general.md + .gitkeep markers
bin/pocket recent [N]         last N sessions across all agents
bin/pocket find <pattern>     grep across every chats/*.jsonl
bin/pocket show <sessionId>   pretty-print one session
bin/pocket tail               follow the active session
bin/pocket doctor             verify deps + layout
bin/pocket help               full list of commands

Files in chats/ follow YYYY-MM-DD_<agent>_<sessionId>.jsonl. Each line is one hook event the agent emitted (UserPromptSubmit, PostToolUse, message.updated, etc.) with secrets scrubbed by hooks/log.sh.

The README has the canonical command table — keep it in sync when you add or change a command (see below).

Self-recursive: delegate pocket CLI work to a subagent

The rule, narrowly scoped to work on this repo's bin/pocket CLI:

  • If the human asks for a new pocket subcommand and you don't already know exactly how to write it, spawn a subagent to implement it instead of researching inside the main chat. The subagent's job is to return a finished cli/src/commands/<name>.ts plus the one-line dispatcher patch and the README row. Main context stays small.

Read the full file on GitHub · 187 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. 2mo ago First seen · 187 lines · 1,880 tokens per session scan A eafc1a09942e

Subscribe to this mod's changes

pocket AGENTS.md is an instructions file published in the GitHub repository filopedraz/pocket (2 stars, last pushed 5mo ago), licensed MIT. It adds 1,880 tokens to every session, about $0.0075 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

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens