What is eddoapp CLAUDE.md?

A project instruction file for the walterra/eddoapp repository. It documents build, test, lint, formatting, logging, and development-server commands, along with rules for where to run them.

Finding the correct commands for building packages, running checks, inspecting logs, and validating commits while avoiding prohibited server-management actions.

It gives coding agents the repository-specific operating rules needed to inspect, build, test, and verify changes correctly.

How walterra/eddoapp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to walterra/eddoapp. 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/walterra/eddoapp/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/walterra/eddoapp

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

Your own site

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

Per session 10,802 This file is loaded in full into every session.

When invoked 10,802 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.10802	$0.10802
Opus 5.5	$0.04321	$0.04321
Sonnet 5.5	$0.02160	$0.02160
Haiku 4.5	$0.01080	$0.01080

Measured 2d ago against content hash 2dc455e4374c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

CLAUDE.md · 1,020 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Build & Test Commands

Commands to run servers

Never run these commands yourself or kill related processes. The user is responsible for running the server. If you need to run or restart one of these commands, ask the user to do it for you.

web (client+api): pnpm dev (port 3000)
web client dev only: pnpm dev:web-client (port 5173 in dev)
web api dev only: pnpm dev:web-api (port 3000, passes through web-client)
MCP server dev: pnpm dev:mcp-server
Telegram bot dev: pnpm dev:telegram-bot

Root Level

Use these commands for investigating, testing and linting. DO NOT cd into packages. you MUST stay in root and run commands like pnpm test|build from the repo root. CRITICAL: Run pnpm check:commit to verify code before requesting a commit.

IMPORTANT: Use pnpm logs:tail to investigate unified logs produced by pnpm dev
Build all packages: pnpm build (always run from the repo root, not from individual package dirs)
Build for production: pnpm build:production
Lint: pnpm lint
Format check: pnpm lint:format
Commit check (required before commit): pnpm check:commit
Validation dependency policy: pnpm check:no-zod (blocks direct Zod imports and dependencies; excludes upstream transitive dependencies)
Format fix: pnpm format
Unit tests (default): pnpm test
Unit tests only: pnpm test:unit
MCP server integration tests: pnpm test:integration:mcp-server (uses vitest with global setup)
Durable agent integration tests: pnpm test:integration:durable (disposable CouchDB, scripted provider, no API calls)
Behavioral agent integration tests: pnpm test:integration:agent-loop (VCR auto mode; missing interactions call the provider)
Record native behavioral cassettes: pnpm test:integration:agent-loop:record (incurs API charges)
Replay native behavioral cassettes: pnpm test:integration:agent-loop:playback (no provider credentials)
E2E tests: pnpm test:e2e
Full test suite: pnpm test:all
CI test suite: pnpm test:ci (includes deterministic Durable integration tests; no model API key required)
Run single test: pnpm vitest:run src/path/to/file.test.ts
TypeScript check: pnpm tsc:check
MCP server test: pnpm test:mcp-server (this lets you run commands against mcp-server)
Check unused dependencies: pnpm knip

Read the full file on GitHub · 1,020 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.

2d ago Changed · +1 lines · +31 tokens per session 2dc455e4374c
14d ago Changed · -13 lines · +247 tokens per session 7ea46f9b6247
2mo ago First seen · 1,032 lines · 10,524 tokens per session scan A 0f472ccb6a02

Subscribe to this mod's changes

eddoapp CLAUDE.md is an instructions file published in the GitHub repository walterra/eddoapp (58 stars, last pushed 3d ago), licensed Apache-2.0. It adds 10,802 tokens to every session, about $0.0432 per session on Opus 5.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-30.

agentic-coding context-management timetracking todo

eddoapp CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
eddoapp CLAUDE.mdwalterra/eddoapp	Instructions file	58	3d ago	Apache-2.0	A	10,802	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

eddoapp: Instructions file for Claude Code