What is aimock CLAUDE.md?

Project instructions for a TypeScript application called aimock, including its folder structure, testing tools, formatting rules, and drift checks. They require formatting, linting, and tests before commits.

Use them when modifying aimock, locating its code or tests, adding test coverage, running validation, or investigating model-family drift.

They provide the checks needed to catch style errors, code issues, and regressions before changes are committed. They also explain where source code, tests, documentation, and fixtures belong.

aimock CLAUDE.md — Instructions file by CopilotKit

Install

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.

agentmods

npx agentmods add instructions/copilotkit/aimock/claude-md

Clone the repo

git clone --depth 1 https://github.com/CopilotKit/aimock

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00525	$0.00525
Opus 5	$0.00262	$0.00262
Sonnet 5	$0.00105	$0.00105
Haiku 4.5	$0.00052	$0.00052

Measured yesterday against content hash e67650cf2ebf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

aimock 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 yesterday.

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.

aimock

Before Every Commit

Run these checks on all changed files before committing:

pnpm run format:check    # prettier
pnpm run lint            # eslint
pnpm run test            # vitest

If prettier or eslint fail, fix with:

npx prettier --write <files>
npx eslint --fix <files>

A pre-commit hook (husky + lint-staged) runs prettier and eslint automatically on staged files, but always verify manually before pushing — CI checks the entire repo, not just staged files.

Project Structure

src/ — TypeScript source (server, router, helpers, responses, types)
src/__tests__/ — Vitest test suite
docs/ — GitHub Pages website (static HTML)
fixtures/ — Example fixture JSON files shipped with the package

Testing

Tests live in src/__tests__/ and use Vitest
When adding features or fixing bugs, add or update tests
Run pnpm test before pushing

Drift Remediation

There is no LLM/agent in the remediation loop. Automated remediation is deterministic and scoped to model-family churn only; general drift is caught by the daily drift test and fixed by a human. Lives in scripts/:

scripts/drift-report-collector.ts — runs drift tests, produces drift-report.json
scripts/drift-sync.ts — zero-LLM model-family sync (mechanical registry edit or needs-human note file) + reusable git/PR plumbing
scripts/drift-sync-check.ts — the deterministic gate (changed-file allowlist, checksum-pin re-assert, clean re-collect) replacing remediation-diff review

See DRIFT.md for full documentation and .github/workflows/fix-drift.yml for the CI workflow.

Forbidden Paths

NEVER commit internal planning documents (specs, plans, design docs) to this repo. No docs/superpowers/, no docs/plans/, no docs/specs/. These are gitignored. Store them in Notion or ~/.claude/ instead.

Commit Messages

This repo enforces conventional commit prefixes via commitlint: fix:, feat:, docs:, test:, chore:, refactor:, etc.
No Co-Authored-By lines

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.

yesterday First seen · 57 lines · 525 tokens per session scan A e67650cf2ebf

Subscribe to this mod's changes

aimock CLAUDE.md is an instructions file published in the GitHub repository CopilotKit/aimock (902 stars, last pushed yesterday), licensed MIT. It adds 525 tokens to every session, about $0.0026 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-30.

Data and AI Git and workflow LLM Testing ai-testing aimock mcp mock-server openai

aimock CLAUDE.md

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

aimock

Before Every Commit

Project Structure

Testing

Drift Remediation

Forbidden Paths

Commit Messages

What this file has done since we first saw it

Other instructions, from other repositories

opik copilot-instructions.md

mockserver-monorepo AGENTS.md

gptme AGENTS.md

GPT-RAG copilot-instructions.md

AstrBot copilot-instructions.md

codexia AGENTS.md