What is weaverkit CLAUDE.md?

Project instructions for Weaverkit, a collection of TypeScript packages for Node.js and Express applications managed together in a Lerna monorepo. A monorepo stores multiple related packages in one repository.

Use it to build all or one Weaverkit package, run tests, check code quality, format files, and prepare or publish package changes.

It gives contributors the correct commands and rules for building, testing, linting, formatting, and publishing the packages. It also explains that tests must be run from the repository root.

weaverkit CLAUDE.md — Instructions file by iyiolapeter

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/iyiolapeter/weaverkit/claude-md

Clone the repo

git clone --depth 1 https://github.com/iyiolapeter/weaverkit

Per session 3,110 This file is loaded in full into every session.

When invoked 3,110 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.03110	$0.03110
Opus 5	$0.01555	$0.01555
Sonnet 5	$0.00622	$0.00622
Haiku 4.5	$0.00311	$0.00311

Measured 2d ago against content hash 3372107e8a0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

weaverkit 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 · 347 lines

How it starts

The opening of the file, as written. The whole thing — 347 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.

Commands

# Build all packages (via lerna) then publish
npm run publish

# Build a single package
cd packages/<name> && npx tsc

# Run all tests
npm test

# Run tests in watch mode
npm run test:watch

# Run a single test file
npm test -- packages/validator/__tests__/validator.test.ts

# Lint / format
npm run lint
npm run lint:fix
npm run format

# Conventional commit helper (commitizen)
npm run commit

# Pre-publish gate: lint-staged + lint:fix + lerna build
npm run prepare:commit

Tests must always be run from the root. Individual packages intentionally throw an error if you run npm test inside them.

Architecture Overview

Weaverkit is a Lerna monorepo of scoped @weaverkit/* packages providing Express-centric utilities for TypeScript/Node.js apps (Node >= 20, CommonJS output, TypeScript 4.9.5 strict mode, decorators enabled).

Package dependency graph

@weaverkit/adapters.base (abstract)
  ├── @weaverkit/adapters.mongoose
  ├── @weaverkit/adapters.redis
  └── @weaverkit/adapters.sequelize

@weaverkit/express
  └── peerDeps: @weaverkit/data, @weaverkit/errors

@weaverkit/logger
  └── @weaverkit/utils

# Standalone (no internal deps):
@weaverkit/errors
@weaverkit/data
@weaverkit/utils
@weaverkit/validator

Package Deep-Dives

`@weaverkit/errors`

Error hierarchy rooted at abstract AppError extends Error.

Concrete classes and HTTP codes:

Class	Code	httpCode
`BadRequestError` / `InvalidArgumentError` / `InvalidActionError`	`BAD_REQUEST_ERROR` etc.	400
`UnauthorizedError`	`UNAUTHORIZED_ERROR`	401
`ForbiddenError`	`FORBIDDEN_ERROR`	403
`NotFoundError`	`NOT_FOUND_ERROR`	404
`ConflictError`	`CONFLICT_ERROR`	409
`UnprocessibleEntityError`	`UNPROCESSIBLE_ENTITY_ERROR`	422
`ValidationError` (extends above)	`INPUT_VALIDATION_ERROR`	422
`FailedDependencyError`	`FAILED_DEPENDENCY_ERROR`	424
`TooManyRequestsError`	`TOO_MANY_REQUESTS_ERROR`	429
`ServerError`	`SERVER_ERROR`	500
`NotImplementedError`	`NOT_IMPLEMENTED_ERROR`	501
`ServiceUnavailableError`	`SERVICE_UNAVAILABLE_ERROR`	503
`HttpError`	dynamic	custom code passed to constructor

Read the full file on GitHub · 347 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 First seen · 347 lines · 3,110 tokens per session scan A 3372107e8a0b

Subscribe to this mod's changes

weaverkit CLAUDE.md is an instructions file published in the GitHub repository iyiolapeter/weaverkit (5 stars, last pushed 1mo ago), licensed MIT. It adds 3,110 tokens to every session, about $0.0155 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.

Backend and APIs Code review Testing

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.

github/spec-kit · 7,104 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

weaverkit CLAUDE.md