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/lemur47/logic/claude-mdgit clone --depth 1 https://github.com/lemur47/logicWrote this? Show the measurements
A badge for your README with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them.
[](https://agentmods.dev/instructions/lemur47/logic/claude-md)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.05288 | $0.05288 |
| Opus 5 | $0.02644 | $0.02644 |
| Sonnet 5 | $0.01058 | $0.01058 |
| Haiku 4.5 | $0.00529 | $0.00529 |
Grade A, and why
logic CLAUDE.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **A build gate can only see the file you ship, not the one your CDN serves.** `site/public/robots.txt` was correct in this repository for months while production served something else entirely: Cloudflare's managed `ro How it starts
The opening of the file, as written. The whole thing — 230 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
Atomic logic for decision-making — turning abstract ideas into executable functions. A modular, privacy-first toolkit built with FastAPI and SQLAlchemy. Five live modules: TCO, PERT, Monte Carlo, EVM, and Bayesian estimation calibration.
The logic repo is the open source foundation of pmo.run — a PMO service combining AI and human expertise. Strategy, audiences, and monetisation: docs/STRATEGY.md. Architecture and technical decisions: docs/DESIGN.md. Sprint actuals: docs/SPRINT_HISTORY.md. Content pipeline: skills/operational/content-cadence/SKILL.md.
Commands
# Install dependencies
uv pip install -e ".[dev]"
# Run API server (hot reload)
uv run uvicorn app.main:app --reload
# Run all tests
pytest
# Run a single test file
pytest tests/test_foo.py
# Run standalone module tests (each module ships its own pytest suite)
pytest examples/standalone/{module}/
# Run standalone example
python examples/standalone/tco/tco.py
# Run the site's parity tests (site/src/lib vs the Python core)
cd site && npm test
# Run the remote-MCP example's parity tests (examples/remote-mcp/src vs the core)
cd examples/remote-mcp && npm test
# Build the site. NOT optional when you have touched site/ — `npm test` covers the
# parity net and the crawlability gate's parsing, but the gate itself only runs
# after `astro build`, because what it checks does not exist until then. CI runs
# `npm test` BEFORE `npm run build`, so a green test run says nothing about it.
cd site && npm run build
# Regenerate BOTH parity fixture sets after changing app/pert or app/tco core.
# The pytest CI job re-runs these and fails on a non-empty diff, so a core change
# that leaves the fixtures behind now goes red instead of quietly netting the two
# TypeScript ports against a core that no longer exists.
uv run python site/scripts/generate_parity_fixtures.py
uv run python examples/remote-mcp/scripts/generate_fixtures.py
# Lint and format
ruff check .
ruff format --check . # check only
ruff format . # auto-fix
# Type check (app/ directory only)
pyright
# Security audit (SAST)
opengrep scan --config auto --config .opengrep/ --scan-unknown-extensions .
# Dependency vulnerability scan (SCA)
# Use --config even though the suppression list is currently EMPTY. This is the
# invocation the pre-commit hook and the CI job both use, so it is what
# reproduces them; drop it and you are testing something else.
# It matters the moment a suppression exists again: without the flag the
# auto-discovered root config does not apply to the nested lockfiles, so osv
# reports the project's own waivers as "unused ignores" and then prints them as
# live findings — indistinguishable from expired suppressions, and the tempting
# "fix" is to edit osv-scanner.toml and weaken a control that was working.
# That symptom is dormant, not gone: the Astro 6->7 upgrade discharged all three
# waivers on 2026-07-31, so there is nothing left for it to misreport today.
osv-scanner scan source --config=osv-scanner.toml --recursive .
# Run all pre-commit hooks
pre-commit run --all-files
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 · 230 lines · 5,288 tokens per session scan A bab5fb15cc2f
logic CLAUDE.md is an instructions file published in the GitHub repository lemur47/logic (2 stars, last pushed 5d ago), licensed MIT. It adds 5,288 tokens to every session, about $0.0264 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
deckforge CLAUDE.md
Instructions for Whatsonyourmind/deckforge, covering deckforge, tech stack, project structure, key commands and local development.
agents
Always-loaded project anchor. Read this first. Contains project identity, non-negotiables, commands, and pointer to .mex/ROUTER.md for full context. Use GitNexus MCP tools for all structural and impact analysis.
loopback-training-server CLAUDE.md
Instructions for aderaaij/loopback-training-server, covering training api, tech stack, project structure, frontend (web dashboard) and development.
mcp-redmine-rest CLAUDE.md
Claude Code instructions for alsimoes/mcp-redmine-rest, covering claude.md, what this is, layout (src-layout), tool registration pattern and deliberately missing tools.
agents
Always-loaded project anchor. Read this first. Contains project identity, non-negotiables, commands, and pointer to ROUTER.md for full context.
emer-ai-tools AGENTS.md
Instructions for emercoin/emer-ai-tools, covering the problem, what this gives you, how it works, trust model and tools (mcp).