Borrowing it
Nothing to install: this file belongs to Stankye/profiler-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Stankye/profiler-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/Stankye/profiler-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/stankye/profiler-mcp/claude-md)<a href="https://agentmods.dev/instructions/stankye/profiler-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/stankye/profiler-mcp/claude-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.1 | $0.00654 | $0.00654 |
| Opus 5 | $0.00327 | $0.00327 |
| Sonnet 5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
profiler-mcp 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 6d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
profiler-mcp
Two MCP servers — vtune (Intel VTune) and uprof (AMD uProf) — one package, one core,
fully self-testable without profiler hardware via byte-realistic mock CLIs.
Commands
uv sync # deps (Python >=3.11, mcp SDK v1.x pinned <2)
uv run pytest # deterministic gate: ALL of layers 1-4. Keep green.
uv run ruff check src tests
make -C examples/workloads # compile the profiling workload (needed by e2e tests)
uv run vtune-mcp # run a server on stdio (uprof-mcp likewise)
Load-bearing invariants
tests/fixtures/*are verbatim vendor output (provenance:docs/research/captures-*.md). Never edit them to make code pass — fix the code. New fixtures require new verbatim captures indocs/research/first.- Mock CLIs (
src/profiler_mcp/mocks/) are strict: unknown flags are errors, so server command-construction bugs surface as test failures. If you add a flag invtune/cli.py/uprof/cli.py, teach the mock the same flag in the same change. - All tool return shapes live in
core/models.py(TypedDicts = wire contract). Change shapes there only, and expect both servers plus tests to move together. - Every result is stamped with its
mode(real/mock); anything user-visible that reports numbers must carry the mock caveat. Never let synthetic numbers pass as real. - The two servers stay structurally parallel: a capability added to one gets added to the
other (or the asymmetry documented, like
uprof_timechart). mcpstays pinned>=1.28,<2until the v2 migration is done deliberately.
Architecture in one breath
server.py (tool surface, FastMCP) → cli.py (argv construction) → core/runner.py
(subprocess) → real binary or mock (resolved by core/config.py; mode auto-detects) →
output → parse.py → TypedDicts from core/models.py; results registered in
core/store.py under short ids (hs-0000); comparisons via core/compare.py return a
verdict that fail_on_regression turns into a hard ToolError (the agentic-loop gate).
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.
- 6d ago First seen · 47 lines · 654 tokens per session scan A 9f23be79287d
profiler-mcp CLAUDE.md is an instructions file published in the GitHub repository Stankye/profiler-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 654 tokens to every session, about $0.0033 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
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.
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.
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).
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).
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.
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.