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/neverinfamous/memory-journal-mcp/copilot-instructionsgit clone --depth 1 https://github.com/neverinfamous/memory-journal-mcpWrote 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/neverinfamous/memory-journal-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/neverinfamous/memory-journal-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/neverinfamous/memory-journal-mcp/copilot-instructions.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.01495 | $0.01495 |
| Opus 5 | $0.00747 | $0.00747 |
| Sonnet 5 | $0.00299 | $0.00299 |
| Haiku 4.5 | $0.00150 | $0.00150 |
Grade A, and why
memory-journal-mcp copilot-instructions.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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Journal MCP — Copilot Code Review Context
Project Overview
Memory Journal MCP is a TypeScript MCP (Model Context Protocol) server providing persistent memory for AI agents. It has 73 tools across 10 groups (core, search, analytics, relationships, io, admin, github, backup, team, codemode), 47 resources, and 19 prompts.
Stack: TypeScript, Vitest, Zod schemas, better-sqlite3 (SQLite), sqlite-vec (vector search), @huggingface/transformers (embeddings), @octokit/rest (GitHub API).
Session Context
Before starting work on this project, read memory://briefing/memory-journal-mcp from the memory-journal-mcp server for real-time context:
- Recent journal entries — what was just worked on by the development agent
- GitHub status — open issues, PRs, explicit CI workflow outcomes, milestones
- Local Git status — clean, modified, or untracked file counts
- Workflow runs — recent CI/CD results
- Copilot review summaries — your own recent review findings
For detailed session handoff context, search for entries tagged session-summary — these contain end-of-session notes from the development agent.
If you find issues during code review, use create_entry with tag copilot-finding to record them for the development agent to see in their next session briefing.
Tooling Standards
- Copilot CLI: Always reference and use
gh copilot, NOT the deprecatedgithub-copilot-cli.
Coding Standards
Naming
- Files and folders: Always kebab-case (
database-adapter.ts,tool-filter.ts,copilot-tools.ts) - Never PascalCase or camelCase for filenames
Modularity
- File size limit: Source files stay under ~500 lines
- Split pattern:
foo.ts→foo/directory with sub-modules +foo/index.tsbarrel re-export - Logical grouping: Split by functional cohesion, not arbitrary line counts
Type Safety
- Strict TypeScript —
tsconfig.jsonenforces strict mode - Never use
eslint-disableto evade standards - Never use
any— useunknownand narrow with type guards - Never use
astype assertions — usesatisfiesoperator or strict type guards - Never use
@ts-ignoreor@ts-expect-error— fix the underlying type issue - Zod schemas for all tool input validation
- Output schemas — All tools have Zod output schemas; error responses must pass validation
- Dual-schema pattern — Relaxed schemas for SDK registration (to handle MCP client coercion), strict schemas inside handlers
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 · 136 lines · 1,495 tokens per session scan A 2400d79e1ce0
memory-journal-mcp copilot-instructions.md is an instructions file published in the GitHub repository neverinfamous/memory-journal-mcp (20 stars, last pushed 1mo ago), licensed MIT. It adds 1,495 tokens to every session, about $0.0075 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
ContextLattice AGENTS.md
Instructions for sheawinkler/ContextLattice, covering agent instructions, start, work loop, hooks and host lifecycle safety.
faf-cli AGENTS.md
Instructions for Wolfe-Jam/faf-cli, covering agents.md — faf-cli, setup & build, run the tests, where things live and conventions.
faf CLAUDE.md
Instructions for Wolfe-Jam/faf, covering claude.md — @faf/specification, what this is, stack, context and 🏎️ claude.md - @faf/specification.
faf-cli copilot-instructions.md
Instructions for Wolfe-Jam/faf-cli, covering github copilot instructions — faf-cli v6, tech stack and project context.
faf-cli CLAUDE.md
Instructions for Wolfe-Jam/faf-cli, covering claude.md — faf-cli, what this is, stack and context.
agent-context-os AGENTS.md
AGENTS.md instructions for conorbronsdon/agent-context-os, covering context os, session lifecycle, lifecycle kernel, context routing and safety.