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 vshulcz/deja-vu --skill deja-searchgit clone --depth 1 https://github.com/vshulcz/deja-vuWrote 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/vshulcz/deja-vu/deja-search)<a href="https://agentmods.dev/skills/vshulcz/deja-vu/deja-search"><img src="https://agentmods.dev/badge/skills/vshulcz/deja-vu/deja-search/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/vshulcz/deja-vu/deja-search"><img src="https://agentmods.dev/badge/skills/vshulcz/deja-vu/deja-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00057 | $0.01159 |
| Opus 5 | $0.00028 | $0.00580 |
| Sonnet 5 | $0.00011 | $0.00232 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
deja-search 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 yesterday.
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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search deja before re-deriving past work: when the user refers to earlier sessions or decisions, before debugging an error, and before implementing something that may already exist. It searches this machine's own history across every AI coding tool used on it, going back further than deja itself was installed.
This skill drives the deja binary through the shell. If the deja MCP tools (recall, recall_context, blame, fix, how, remember) are available in this session, use those instead — same index, one less hop. They appear only when deja install has wired this harness.
Finding something
deja search --json "<query>": the most specific token available — an exact error string, function name, file path, or flag. Several words are ANDed. Only this user's own sessions, never library docs or general knowledge.deja ctx <query|id-prefix>: a full digest of the single best-matching session, once a hit looks right and the reasoning behind it matters. Takes no flags.deja show <id-prefix> --harness <name> --json: the turns themselves, paged with--offsetand--limit. Use the id and harness a hit printed.deja blame <path> --json: before editing, refactoring or deleting a file, the prior sessions that discussed it, so you know why it is shaped the way it is. Session history, not git authorship.deja fix "<pasted error>": the commands that followed that same error before, in sessions where it did not come back. Paste the failing output verbatim.deja how <what>: the real command with the real flags this machine runs for a build, test, deploy or script, ordered by how many sessions ran it. A guessed invocation is plausible and fails on this setup.deja remember "<text>": store one durable decision after it is settled, as a single self-contained fact. Not transcripts, not anything already obvious from the code.
Useful flags on search: --harness, --project, --since 30d, --role user|assistant|tool|files|command|edit, --session <id>, --limit 1-100, --all, --re for a regular expression.
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.
- yesterday Changed 3c0cc38c8ad3
- 2d ago Changed 50e77febedcc
- 6d ago Changed · +13 lines · +6 tokens per session 594b8ead0824
- 10d ago First seen · 41 lines · 51 tokens per session scan A c2d85ee7ce73
deja-search is a skill published in the GitHub repository vshulcz/deja-vu (796 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 1,159 once invoked, about $0.0003 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 skills, from other repositories
dreaming
Maintain Signet's living ontology and memory substrate from transcripts, memory artifacts, source artifacts, notes, summaries, and imported records.
signet-recall
Use Signet-specific recall and source search from Codex without confusing it with Codex native memory.
signet-save-note
Save explicit notes into Codex native memory through Signet.
signet-sessions
Search Signet transcript/session evidence from Codex.
plur-create-engrams
Create or improve PLUR engrams from conversations, documents, decisions, observations, and explicit preferences. Use for memory extraction, engram authoring, or reviewing proposed memories, including global, scoped, pinned, retrieved, and provisional knowledge. Ordinary use of existing memories does not require this…
plur-memory
Persistent learning for AI agents. Open engram format. Your agent learns from corrections, remembers across sessions, and transfers knowledge across domains.