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 agentmods add instructions/letsdev-it/sessfind/agents-mdgit clone --depth 1 https://github.com/letsdev-it/sessfindWhat 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 | $0.00811 | $0.00811 |
| Opus 5 | $0.00405 | $0.00405 |
| Sonnet 5 | $0.00162 | $0.00162 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
sessfind 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 2d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guidelines for AI assistants and contributors
Product specification and SDD
The product contract for sessfind lives in the letsdev-it/sdd-specs
repository. Treat the current product spec as authoritative for observable
behavior.
- Contract changes start as
spec-featureorspec-choreissues in the spec repository and are implemented only after the resulting code task exists. - Bugs and maintenance work start as
code-bugorcode-choreissues in the spec repository. - Every pull request must close or reference its generated
sdd:taskissue. - Do not introduce observable behavior that is absent from, or contradicts, the current product spec. Route contract changes through the spec first.
- Update the relevant technical-spec document under
spec/in the same pull request when the implementation architecture or conventions change.
Product clarification
When implementation discovers a missing or ambiguous product decision,
do not invent behavior in code. Add this comment to the open sdd:task issue
in this code repository (not to the PR and not directly to the spec repo):
/sdd clarify <focused product question>
Valid product questions include:
/sdd clarify Should sessions without a project be included in an unfiltered list?
/sdd clarify What should the CLI display when a stored session source is no longer installed?
/sdd clarify Should deleting an indexed source also remove its cached semantic data?
Do not use clarification for implementation choices:
/sdd clarify Should this use an enum or a trait object?
/sdd clarify Which Rust crate should implement date parsing?
/sdd clarify How should this module be split?
Those are technical decisions owned by this repository and may be recorded in
its technical spec or an implementation ADR. Clarification keeps the existing
task and branch, marks the task sdd:blocked-product, and creates a focused
draft spec PR. Resume after the product decision is merged and an approved
update operation removes the blocked label.
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.
- 2d ago First seen · 91 lines · 811 tokens per session scan A ced9f013f3b0
sessfind AGENTS.md is an instructions file published in the GitHub repository letsdev-it/sessfind (23 stars, last pushed 1mo ago), licensed MIT. It adds 811 tokens to every session, about $0.0041 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-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain 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.