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/veedubin/super-memory-ts/agents-mdgit clone --depth 1 https://github.com/Veedubin/Super-Memory-TSWrote 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/instructions/veedubin/super-memory-ts/agents-md)<a href="https://agentmods.dev/instructions/veedubin/super-memory-ts/agents-md"><img src="https://agentmods.dev/badge/instructions/veedubin/super-memory-ts/agents-md.svg" alt="Measured on agentmods" 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 | $0.01852 | $0.01852 |
| Opus 5 | $0.00926 | $0.00926 |
| Sonnet 5 | $0.00370 | $0.00370 |
| Haiku 4.5 | $0.00185 | $0.00185 |
Grade A, and why
Super-Memory-TS 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 3d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Super-Memory-TS
Role: NPM-publishable MCP server with local embeddings and vector search
Package: @veedubin/super-memory-ts
Repository: https://github.com/Veedubin/Super-Memory-TS
License: MIT
Current Version: v2.6.5
Why This Exists
This project provides a local-first semantic memory system with project isolation, tiered search strategies, and MCP protocol integration for AI assistants like Boomerang.
Architecture (v2.6.5)
| Component | Technology | Notes |
|---|---|---|
| Database | Qdrant (v1.7+) | HNSW indexing, payload filtering |
| Embeddings | BGE-Large (1024-dim, GPU) / MiniLM-L6-v2 (384-dim, CPU) | fp16 precision by default |
| Protocol | MCP (Model Context Protocol) | stdio/HTTP modes |
| Integration | Built-in for Boomerang v2 | Zero-overhead direct imports |
Key Features
- Project Isolation: Payload-based filtering via
BOOMERANG_PROJECT_ID - Custom Path Indexing:
index_projecttool accepts custompathparameter - Tiered Search:
tiered(default): Fast Reply - MiniLM + BGE fallbackparallel: Archivist - Dual-tier RRF fusion for maximum recall
Commands
| Command | Purpose |
|---|---|
npm run build |
Compile TypeScript to dist/ |
npm run typecheck |
Type-check without emitting (tsc --noEmit) |
npm run prepublishOnly |
Runs npm run build before publish |
npm run dev |
Watch mode with tsx |
npm run test |
Run tests with bun test |
npm run lint |
ESLint on src/ |
Publishing
Trigger
Pushing a semver tag triggers .github/workflows/npm-publish.yml:
git tag v1.0.0
git push origin v1.0.0
Workflow Details
- Trigger:
pushon tags matchingv*.*.* - Node version: 22
- Scope:
@veedubin - Provenance: Enabled (
id-token: write) - Secret required:
NPM_PUBLISH_TOKEN
Pre-Publish Checklist
NPM_PUBLISH_TOKENsecret is set in GitHub repo settingspackage.jsonversion bumped appropriatelynpm run typecheckpassesnpm run buildsucceeds anddist/is generated- Tag pushed in
vX.Y.Zformat
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.
- 3d ago First seen · 182 lines · 1,852 tokens per session scan A 4db39d66540c
Super-Memory-TS AGENTS.md is an instructions file published in the GitHub repository Veedubin/Super-Memory-TS (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,852 tokens to every session, about $0.0093 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 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).
spec-kit AGENTS.md
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.
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.
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.
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).
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.