What is MCP-Metrics CLAUDE.md?

Project instructions for MCP-Metrics, including setup and usage guidance for GBrain. GBrain is a local search tool that can find code and stored notes by meaning, symbols, callers, and dependencies.

Use it to search the repository and curated memory, find where concepts or symbols are handled, and inspect what calls or depends on a piece of code.

It helps an agent choose semantic code search when exact text or identifiers are unknown, and gives it rules for using the configured local index.

How abhishekshankar/MCP-Metrics configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to abhishekshankar/MCP-Metrics. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/abhishekshankar/MCP-Metrics/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/abhishekshankar/MCP-Metrics

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/abhishekshankar/mcp-metrics/claude-md/github.svg)](https://agentmods.dev/instructions/abhishekshankar/mcp-metrics/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/abhishekshankar/mcp-metrics/claude-md"><img src="https://agentmods.dev/badge/instructions/abhishekshankar/mcp-metrics/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/abhishekshankar/mcp-metrics/claude-md"><img src="https://agentmods.dev/badge/instructions/abhishekshankar/mcp-metrics/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 616 This file is loaded in full into every session.

When invoked 616 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00616	$0.00616
Opus 5	$0.00308	$0.00308
Sonnet 5	$0.00123	$0.00123
Haiku 4.5	$0.00062	$0.00062

Measured 8d ago against content hash 5246ecdc4613, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

MCP-Metrics CLAUDE.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 8d 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.

CLAUDE.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

GBrain Configuration (configured by /setup-gbrain)

Mode: local-stdio
Engine: pglite
Config file: ~/.gbrain/config.json (mode 0600)
Setup date: 2026-06-28
MCP registered: yes (user scope)
Artifacts sync: off
Current repo policy: read-write
Trust policy: personal (single-tenant local brain)

GBrain Search Guidance (configured by /sync-gbrain)

GBrain is set up and synced on this machine. The agent should prefer gbrain over Grep when the question is semantic or when you don't know the exact identifier yet. Two indexed corpora available via the gbrain CLI:

This repo's code (registered as gstack-code-<repo> source).
~/.gstack/ curated memory (registered as gstack-brain-<user> source via the existing federation pipeline).

Prefer gbrain when:

"Where is X handled?" / semantic intent, no exact string yet: gbrain search "<terms>" or gbrain query "<question>"
"Where is symbol Y defined?" / symbol-based code questions: gbrain code-def <symbol> or gbrain code-refs <symbol>
"What calls Y?" / "What does Y depend on?": gbrain code-callers <symbol> / gbrain code-callees <symbol>
"What did we decide last time?" / past plans, retros, learnings: gbrain search "<terms>" --source gstack-brain-<user>

Grep is still right for known exact strings, regex, multiline patterns, and file globs. The brain auto-syncs incrementally on every gstack skill start. Run /sync-gbrain to force-refresh, /sync-gbrain --full for full reindex.

Skill Routing

When the user's request matches an available skill, invoke it via the Skill tool. When in doubt, invoke the skill.

Key routing rules:

Product ideas/brainstorming → invoke /office-hours
Strategy/scope → invoke /plan-ceo-review
Architecture → invoke /plan-eng-review
Design system/plan review → invoke /design-consultation or /plan-design-review
Full review pipeline → invoke /autoplan
Bugs/errors → invoke /investigate
QA/testing site behavior → invoke /qa or /qa-only
Code review/diff check → invoke /review
Visual polish → invoke /design-review
Ship/deploy/PR → invoke /ship or /land-and-deploy
Save progress → invoke /context-save
Resume context → invoke /context-restore
Author a backlog-ready spec/issue → invoke /spec

Read the full file on GitHub · 57 lines

Changes

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.

8d ago First seen · 57 lines · 616 tokens per session scan A 5246ecdc4613

Subscribe to this mod's changes

MCP-Metrics CLAUDE.md is an instructions file published in the GitHub repository abhishekshankar/MCP-Metrics (0 stars, last pushed 2mo ago), licensed MIT. It adds 616 tokens to every session, about $0.0031 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.

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

MCP-Metrics: Instructions file for Claude Code