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 skills/driftya/code-meridian/codemeridian-contextnpx skills add Driftya/code-meridian --skill codemeridian-contextgit clone --depth 1 https://github.com/Driftya/code-meridianWhat 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.00029 | $0.01349 |
| Opus 5 | $0.00015 | $0.00674 |
| Sonnet 5 | $0.00006 | $0.00270 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
codemeridian-context 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeMeridian Context Skill
Use this skill when working in a repository indexed by CodeMeridian.
The goal is to gather the smallest useful context pack before reading many files or making code changes.
projectContext can be found in meridian.json in field project.
When To Use
Use this skill before:
- implementing a non-trivial change
- planning or starting a feature from a request or
docs/features/*.md - refactoring code
- deleting code
- changing public APIs
- debugging unfamiliar behavior
- reviewing impact
- planning tests
- modifying architecture-sensitive code
If the task touches HTML, CSS, SCSS, selectors, style imports, or CSS variables, pair this skill with codemeridian-frontend so the context routing stays frontend-aware.
Workflow
1. Check Graph Freshness
When exact file targets, symbol names, or relationships matter, check whether the graph is fresh.
Prefer:
check_graph_freshnessfind_graph_drift
If the graph is stale, incomplete, or uncertain, say so before relying on exact results.
Session Evidence
During an implementation session, always record provider-neutral session evidence under .meridian/sessions/*.jsonl so codemeridian evaluate-session can measure whether CodeMeridian helped.
Write one compact JSON object per line. Omit fields that do not apply.
Use this event shape:
{"timestamp":"<ISO-8601 UTC time>","provider":"<codex|copilot|claude|continue|other>","project":"MyApp","kind":"<graph-call|codemeridian-tool|suggestion|tool-result|command|manual-fallback|test-run|stale-warning>","toolName":"<CodeMeridian MCP tool name when applicable>","command":"<shell command when applicable>","targetConfidence":"<exact|file-only|heuristic|stale, comma-separated if needed>","staleWarning":<true|false>,"contextPackStatus":"<full|degraded|failed when recording build_minimal_context results>","changeKind":"<direct-edit|extract|move|rename|split when lineage applies>","derivedFromFiles":["<repo-relative suggested source file>"],"derivedFromSymbols":["<source symbol when known>"],"plannedFolders":["<repo-relative target folder>"],"plannedNamespaces":["<target namespace>"],"files":["<repo-relative file path>"],"tests":["<repo-relative test file path>"]}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 163 lines · 29 tokens per session scan A daa5f1ad2d9d
codemeridian-context is a skill published in the GitHub repository Driftya/code-meridian (4 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 1,349 once invoked, about $0.0001 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 skills, from other repositories
graph
Whole-codebase structural map of the codanna index as one self-contained HTML disc. Wedges per top-level module, concentric rings with hubs at the centre, hover or click a symbol to light its edge web, search, hide or highlight modules, brush a date range on the ribbon timeline (symbols dated by git blame), heatmap of…
x-ray
Deep codebase exploration using semantic search and relationship mapping. Use when you need to understand the current codebase.
use-ivygrep
Gather focused local repository context with ivygrep before implementing, debugging, reviewing, or explaining code. Use for coding tasks involving unfamiliar paths, branch changes, stack traces, architectural relationships, callers, dependents, tests, configuration, or documentation. Prefer one bounded context pack…
memtrace-first
Route code discovery, debugging, flow tracing, how-code-works questions, and pre-edit rationale checks in indexed source-code repos to Memtrace graph plus Cortex decision tools. Use first before searching/reading code, and before editing, refactoring, deleting, or re-picking an approach that may have a recorded…
memtrace-style-fingerprint
Pull the codebase's empirical style norm from Memtrace and match it when writing or editing source code in an indexed repo. Use when choosing between competing idioms (ternary vs if-else, arrow vs function declaration, const vs let, await vs .then, early-return vs nested-return), matching naming case, or when the user…
memtrace-decision-memory
Use Cortex decision memory through the normal Memtrace MCP tools. Trigger for free-text questions about what was decided, chosen, rejected, banned, or established as a convention; for why a symbol exists or which contracts constrain it; for whether a known decision held, drifted, or was violated; and for the…