knowledge-server CLAUDE.md

Repository instructions for coding agents working on the Knowledge Server project. They explain how to activate the environment, run tests, handle AWS Bedrock tests, and check code quality.

In plain words
What is it for?
For setting up the virtual environment, running the regular pytest suite, running Bedrock-only or full tests, and using the project's test and formatting conventions.
Why use it?
They tell an agent which commands and test groups to use, including tests that are skipped by default because they call AWS Bedrock.

Instructions file

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/bwarzecha/knowledge-server/claude-md
Clone the repo
git clone --depth 1 https://github.com/bwarzecha/knowledge-server
Per session 375 This file is loaded in full into every session.
When invoked 375 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.

ModelPer sessionOnce invoked
Fable 5 $0.00375 $0.00375
Opus 5 $0.00187 $0.00187
Sonnet 5 $0.00075 $0.00075
Haiku 4.5 $0.00038 $0.00038

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

Security

Grade A, and why

knowledge-server 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 · 54 lines

What it actually says

Development Tips

  • Always source venv before running any command

Testing and Code Quality

Running Tests

Tests use a fast embedding model (sentence-transformers/all-MiniLM-L6-v2) for speed. Most tests that were previously slow should now complete quickly.

source venv/bin/activate
python -m pytest tests/ -v

Bedrock Tests

Tests that require AWS Bedrock (LLM calls) are marked with @pytest.mark.bedrock and are skipped by default to keep tests fast. To run them:

# Run only bedrock tests
python -m pytest tests/ -m bedrock -v

# Run all tests including bedrock
python -m pytest tests/ -m "not slow" -v

# Run everything (including bedrock and slow tests)
python -m pytest tests/ --tb=short

Test Environment Configuration

The project includes a .env.test file with optimized settings for testing:

  • Fast embedding model: sentence-transformers/all-MiniLM-L6-v2 (22M parameters)
  • MPS device for fast GPU acceleration on Apple Silicon
  • Reduced token limits for faster processing

If you need to test with production embedding models, temporarily modify the test files or use the main .env configuration.

Code Formatting

The project uses black (line length 100), isort, and flake8 for code formatting and linting:

source venv/bin/activate
black src/ tests/
isort src/ tests/
flake8 src/ tests/

Pre-commit Cleanup

Before committing, run the complete cleanup:

source venv/bin/activate
black src/ tests/
isort src/ tests/
python -m pytest tests/
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.

  1. yesterday First seen · 54 lines · 375 tokens per session scan A b3c6e0fdce3e

Subscribe to this mod's changes

knowledge-server CLAUDE.md is an instructions file published in the GitHub repository bwarzecha/knowledge-server (0 stars, last pushed 1y ago), licensed MIT. It adds 375 tokens to every session, about $0.0019 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.

Related

Other instructions, from other repositories

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

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,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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

microsoft/vscode · 5,001 tokens

next.js 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