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.
npx agentmods add instructions/nobelk/random-number-server/claude-mdgit clone --depth 1 https://github.com/nobelk/random-number-serverWrote 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.
[](https://agentmods.dev/instructions/nobelk/random-number-server/claude-md)<a href="https://agentmods.dev/instructions/nobelk/random-number-server/claude-md"><img src="https://agentmods.dev/badge/instructions/nobelk/random-number-server/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.00921 | $0.00921 |
| Opus 5 | $0.00461 | $0.00461 |
| Sonnet 5 | $0.00184 | $0.00184 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
random-number-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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 133 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.
Project Overview
This is a Python-based MCP (Model Context Protocol) server that generates random numbers using weather data as seeds. The server uses FastMCP framework and exposes a tool for generating random numbers based on weather API data.
Architecture
- src/RandomNumberGenerator.py: Core random number generation logic using Linear Congruential Generator algorithm with weather data as seeds
- src/random_server.py: FastMCP server implementation that exposes the random number generation as an MCP tool
- tests/: Comprehensive unit tests with 86% code coverage
Development Commands
Setup and Dependencies
# Install dependencies using uv
uv sync
# Build/install the project in editable mode
uv pip install -e .
Running the Server
Option 1: Using Docker Compose (Recommended)
# Build and run with Docker Compose
docker-compose up -d
# View logs
docker-compose logs -f
# Stop the server
docker-compose down
Option 2: Using uv directly
# Run the MCP server (from project root)
uv run src/random_server.py
# Or with absolute path
uv --directory /Users/Nobel.Khandaker/sources/random-number-server run src/random_server.py
Testing
# Run all tests locally
uv run pytest
# Run tests with coverage report
uv run pytest --cov=src --cov-report=term-missing
# Run specific test file
uv run pytest tests/test_random_number_generator.py
uv run pytest tests/test_random_server.py
# Run tests with verbose output
uv run pytest -v
# Run tests in Docker container
docker-compose run --rm --entrypoint /app/.venv/bin/python random-server -m pytest
Docker Configuration
Files
- Dockerfile: Multi-stage build with Python 3.13 Alpine, optimized to ~110MB
- docker-compose.yml: Production configuration with resource limits and logging
- docker-compose.dev.yml: Development overrides with live code reloading
- .env.example: Environment variable template
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.
- 3d ago First seen · 133 lines · 921 tokens per session scan A 4b860c92f676
random-number-server CLAUDE.md is an instructions file published in the GitHub repository nobelk/random-number-server (0 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 921 tokens to every session, about $0.0046 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.
Other instructions, from other repositories
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).
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.
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.
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.
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).
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.