Borrowing it
Nothing to install: this file belongs to gtkcyber/compact_prompt. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gtkcyber/compact_prompt/master/CLAUDE.mdgit clone --depth 1 https://github.com/gtkcyber/compact_promptWrote 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/gtkcyber/compact_prompt/claude-md)<a href="https://agentmods.dev/instructions/gtkcyber/compact_prompt/claude-md"><img src="https://agentmods.dev/badge/instructions/gtkcyber/compact_prompt/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.1 | $0.02476 | $0.02476 |
| Opus 5 | $0.01238 | $0.01238 |
| Sonnet 5 | $0.00495 | $0.00495 |
| Haiku 4.5 | $0.00248 | $0.00248 |
Grade A, and why
compact_prompt 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 6d 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 — 193 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.
compactprompt is a Python library implementing the four prompt/data compression
strategies from CompactPrompt: A Unified Pipeline for Prompt and Data Compression
in LLM Workflows (Choi et al., 2025, arXiv:2510.18043).
It is an independent, distilled reimplementation — not a port of the authors'
reference notebook (which lives one directory up and is a 35-task, config-driven
research harness; this package deliberately collapses that into a one-line API).
Commands
# Tests (full suite; optional-dep tests skip when their extras are absent)
pytest
pytest tests/test_ngram.py # one file
pytest tests/test_ngram.py::test_round_trip_is_lossless # one test
pytest -rs # show skip reasons
# Lint (CI gate; must stay at 10.00/10). CI runs over all tracked Python files:
pylint $(git ls-files '*.py')
# Install for development
pip install -e . # zero-dep core only
pip install -e '.[all,dev]' # everything + pytest, faithful to paper
python -m spacy download en_core_web_sm # needed for phrase-level pruning
# Runnable tour of every strategy
python examples/quickstart.py
# CLI: review / compact markdown files and Claude Code skills (entry point in cli.py)
compactprompt review ./skills
compactprompt compact FILE.md --engine builtin # dry run
compactprompt compact FILE.md --engine caveman --apply # writes + .bak
# Interactive demo (Prompt + Files & Skills tabs)
streamlit run compactprompt_app.py
# Build the docs site (MkDocs); CI/Read the Docs build must stay clean
pip install -e '.[docs]' && mkdocs build --strict
CI runs two workflows (.github/workflows/): pylint.yml and tests.yml. The
tests.yml core job installs the package with no extras across Python
3.9–3.13; the full job installs .[all,dev] + the spaCy model.
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.
- 6d ago First seen · 193 lines · 2,476 tokens per session scan A 16f0c9501b22
compact_prompt CLAUDE.md is an instructions file published in the GitHub repository gtkcyber/compact_prompt (0 stars, last pushed 1mo ago), licensed MIT. It adds 2,476 tokens to every session, about $0.0124 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.