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/jvpalma/dotrun/claude-mdgit clone --depth 1 https://github.com/jvPalma/dotrunWrote 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/jvpalma/dotrun/claude-md)<a href="https://agentmods.dev/instructions/jvpalma/dotrun/claude-md"><img src="https://agentmods.dev/badge/instructions/jvpalma/dotrun/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.07688 | $0.07688 |
| Opus 5 | $0.03844 | $0.03844 |
| Sonnet 5 | $0.01538 | $0.01538 |
| Haiku 4.5 | $0.00769 | $0.00769 |
Grade A, and why
dotrun 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 4d 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 — 551 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
DotRun (dr) is a unified Bash script management framework that provides instant access to custom scripts, aliases, and configurations from anywhere. It supports Bash, Zsh, and Fish shells.
Version: 3.1.3
Development Setup
# Clone and set up development environment
./dev.sh
# Get help on setup script
./dev.sh --help
The dev.sh script sets up a complete development environment with 7 steps:
- Symlinks
drbinary to~/.local/share/dotrun/ - Symlinks
.dr_config_loaderfor shell integration - Symlinks core feature modules (
core/*.sh) andhelp-messages/directory tree - Symlinks helper utilities (
helpers/*.sh) - Symlinks VERSION file
- Symlinks shell integration files for Bash, Zsh, and Fish (with stale symlink cleanup)
- Creates
~/.local/bindirectory for binary access
This creates symlinks from ~/.local/share/dotrun to core/shared/dotrun/, enabling live testing without reinstallation. The script validates required files (core/shared/dotrun/dr and core/shared/dotrun/ structure) before proceeding.
v3.1.3 updates:
- Symlinks entire
core/help-messages/directory tree (replaces old file-by-file copying) - Cleans stale symlinks in shell directories before creating new ones (removes dangling links from deleted source files)
Logging design: The script uses color-coded output functions (info, success, warning, error) with unicode indicators for clear progress tracking during development setup.
Common Commands
# Linting (ShellCheck is required)
shellcheck core/shared/dotrun/dr
find core/shared/dotrun -name "*.sh" -exec shellcheck {} +
# Test core workflows manually
dr set test-script # Create script
dr test-script # Run script
dr -L # List with docs
dr -a set test # Create alias file
dr -c set test # Create config file
dr -col list # List collections
dr reload # Reload shell config (applies alias/config changes)
dr upgrade --check # Check for updates
dr upgrade # Upgrade to latest version
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.
- 4d ago First seen · 551 lines · 7,688 tokens per session scan A 0c9d93b9c923
dotrun CLAUDE.md is an instructions file published in the GitHub repository jvPalma/dotrun (10 stars, last pushed 5mo ago), licensed MIT. It adds 7,688 tokens to every session, about $0.0384 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
a-i--skills 03-development-workflow.instructions.md
Instructions for organvm-iv-taxis/a-i--skills, covering development workflow instructions, no repo-wide build system, common development commands, after adding/modifying skills and validation before committing.
context-to-action-skills AGENTS.md
Instructions for tmusser/context-to-action-skills, covering agents, repo model, safety rules, output rules and validation commands.
piratebao copilot-instructions.md
Instructions for d4551/piratebao: PirateBao kraken active by default. Respond like pirate captain packing dumpling cargo: dense, exact, no wasted wrap.
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.