Borrowing it
Nothing to install: this file belongs to ArchiveBox/abx-dl. 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/ArchiveBox/abx-dl/main/CLAUDE.mdgit clone --depth 1 https://github.com/ArchiveBox/abx-dlWrote 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/archivebox/abx-dl/claude-md)<a href="https://agentmods.dev/instructions/archivebox/abx-dl/claude-md"><img src="https://agentmods.dev/badge/instructions/archivebox/abx-dl/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/archivebox/abx-dl/claude-md"><img src="https://agentmods.dev/badge/instructions/archivebox/abx-dl/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00571 | $0.00571 |
| Opus 5.5 | $0.00228 | $0.00228 |
| Sonnet 5.5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
abx-dl 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 25d 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.
plugin_info="$(uv run --no-sync --no-sources abx-dl plugins wget)" How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Instructions for abx-dl
Use AGENTS.md as the canonical repository guide. Keep this
checkout on main, use uv for Python commands, and exercise real CLI,
plugin, subprocess, network, and filesystem paths in tests. Do not add skips,
xfails, retries, fake hooks, fake binaries, fake buses, or fallback binary
resolution.
Development setup
set -Eeuo pipefail
uv sync --locked --dev --no-sources
help_output="$(uv run --no-sync --no-sources abx-dl --help)"
grep -q 'Usage:' <<<"$help_output"
Inspect the installed plugin surface
set -Eeuo pipefail
plugin_info="$(uv run --no-sync --no-sources abx-dl plugins wget)"
grep -q 'WGET_BINARY=wget' <<<"$plugin_info"
grep -q 'on_Snapshot__35_wget' <<<"$plugin_info"
Verification
The normal CI workflow assigns every repository test file exactly once across
Linux, macOS, and every supported Python minor version. It also runs a real crawl
across every Snapshot hook from the pinned abx-plugins release. The Docker
workflow builds and tests both amd64 and arm64 images. Documentation snippets,
including those marked docker_required, run twice daily when the source has
changed since the last successful docs run. Docker snippets use the published
image for that exact source revision.
Run the repository's complete static verification before publishing changes:
set -Eeuo pipefail
uv run --no-sync --no-sources prek run --all-files
Releases
Releases are automatic from main. Bump the version and its lockfile, commit,
and push. The release workflow waits for the exact commit's test workflow,
creates the matching GitHub release and tag, waits for the exact Docker build,
and publishes the package through PyPI trusted publishing. Do not create or
push tags locally.
Architecture
- Plugin discovery comes from the installed
abx-pluginspackage or the explicitABX_PLUGINS_DIRoverride. - Required binaries are emitted as
BinaryRequestEventrecords and resolved only byabxpkg; host binaries are considered before managed providers. - Resolved host and managed binaries are projected into
ABXPKG_LIB_DIR/env/bin.ABXPKG_LIB_DIR/binis only a human convenience surface and must never be used programmatically. - Crawl setup and snapshot hooks run through the unified event state machine. Chrome readiness uses its plugin-owned file mechanism rather than a generic bus-level readiness event.
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.
- 25d ago Changed · +2 lines · +24 tokens per session 3f8be7e3a448
- 2mo ago First seen · 62 lines · 547 tokens per session scan A 22d3f89a0a7b
abx-dl CLAUDE.md is an instructions file published in the GitHub repository ArchiveBox/abx-dl (149 stars, last pushed today), licensed MIT. It adds 571 tokens to every session, about $0.0023 per session on Opus 5.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-30.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.