What is hejdar-mcp CLAUDE.md?

Project instructions for hejdar-mcp, covering secure coding practices and Git rules. They require protecting secrets, validating inputs, limiting permissions and committing code changes properly.

Developing and reviewing hejdar-mcp while checking secret handling, access controls, external connections and required Git actions.

They reduce common security risks and make code changes easier to track and review.

How ARKALDA/hejdar-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to ARKALDA/hejdar-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.

Copy the file

curl -O https://raw.githubusercontent.com/ARKALDA/hejdar-mcp/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/ARKALDA/hejdar-mcp

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/arkalda/hejdar-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/arkalda/hejdar-mcp/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/arkalda/hejdar-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/arkalda/hejdar-mcp/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/arkalda/hejdar-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/arkalda/hejdar-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 165 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.00165	$0.00165
Opus 5	$0.00082	$0.00082
Sonnet 5	$0.00033	$0.00033
Haiku 4.5	$0.00016	$0.00016

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

Security

Grade A, and why

hejdar-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 9d 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 · 22 lines

What it actually says

Hejdar MCP — Project Instructions

Security principles

All code must follow security-by-design:

Secrets in environment variables only, never in code, logs, or API responses
Input validation on all external-facing endpoints
Least privilege: scoped API keys, minimal permissions
No sensitive data in error messages or stack traces
TLS enforced for all external communication

Git discipline

Every prompt that modifies code MUST end with:

git add -A
git commit with a descriptive message following conventional commits (fix:, feat:, chore:, docs:)
git push to origin/master

Never leave uncommitted changes. If the prompt is read-only (tests, analysis), state "No changes to commit" explicitly.

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.

9d ago First seen · 22 lines · 165 tokens per session scan A 92146b922161

Subscribe to this mod's changes

hejdar-mcp CLAUDE.md is an instructions file published in the GitHub repository ARKALDA/hejdar-mcp (1 stars, last pushed 4mo ago), licensed MIT. It adds 165 tokens to every session, about $0.0008 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

hejdar-mcp: Instructions file for Claude Code