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-frontendnpx skills add Driftya/code-meridian --skill codemeridian-frontendgit clone --depth 1 https://github.com/Driftya/code-meridianWrote 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/driftya/code-meridian/codemeridian-frontend)<a href="https://agentmods.dev/skills/driftya/code-meridian/codemeridian-frontend"><img src="https://agentmods.dev/badge/skills/driftya/code-meridian/codemeridian-frontend.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.00043 | $0.01279 |
| Opus 5 | $0.00022 | $0.00639 |
| Sonnet 5 | $0.00009 | $0.00256 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade A, and why
codemeridian-frontend 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeMeridian Frontend Skill
Use this skill when working in a repository indexed by CodeMeridian and the task touches frontend markup, selectors, stylesheets, CSS variables, or style cleanup.
The goal is to make frontend work use the indexed HTML/CSS/SCSS relationship graph instead of falling back to file-by-file guessing.
projectContext can be found in meridian.json in field project.
When To Use
Use this skill when the request includes words or intent like:
- frontend
- HTML
- CSS
- SCSS
- selector
- stylesheet
- class rename
- what styles affect this
- what markup uses this class
- component and stylesheet relationship
- cascade
- specificity
- duplicate style values
- style token cleanup
Also use this skill when the edit target is a frontend component, template, markup file, stylesheet, or selector-related behavior.
Core Rule
Prefer generic CodeMeridian tools first.
Use dedicated frontend-specific analysis only when the question is not a good fit for the existing generic surfaces.
Frontend-aware generic tools should remain the default for:
- impact
- implementation surface
- minimal edit context
- connection tracing
- duplicate analysis when the question is still "what is similar"
Use frontend-specific tools only for questions like cascade conflicts or selector-specific style cleanup.
Frontend Graph Signals
Expect useful answers from indexed frontend edges such as:
UsesClassUsesIdDefinesSelectorImportsStyleUsesCssVariableDefinesCssVariable
Treat these as first-class relationships when analyzing frontend work.
Workflow
1. Check Graph Freshness
Before trusting exact class, selector, or stylesheet relationships, verify graph freshness.
Prefer:
check_graph_freshnessfind_graph_drift
If freshness is stale or unknown, say so before making rename, delete, or impact claims.
2. Build Frontend Context First
Start with the same generic workflow used for backend code, but expect frontend relationships to appear in the result.
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 · 213 lines · 43 tokens per session scan A e0aec4f059a9
codemeridian-frontend is a skill published in the GitHub repository Driftya/code-meridian (4 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 1,279 once invoked, about $0.0002 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…