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 rules/d-padmanabhan/agent-engineering-handbook/150-justfilegit clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbookWrote 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/rules/d-padmanabhan/agent-engineering-handbook/150-justfile)<a href="https://agentmods.dev/rules/d-padmanabhan/agent-engineering-handbook/150-justfile"><img src="https://agentmods.dev/badge/rules/d-padmanabhan/agent-engineering-handbook/150-justfile.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.00014 | $0.03173 |
| Opus 5 | $0.00007 | $0.01587 |
| Sonnet 5 | $0.00003 | $0.00635 |
| Haiku 4.5 | $0.00001 | $0.00317 |
Grade C, and why
150-justfile scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf dist/ node_modules/.cache/ How it starts
The opening of the file, as written. The whole thing — 572 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Justfile Engineering Ruleset
Goal: Standardized justfile patterns that provide consistent, discoverable commands across all projects regardless of underlying technology.
Why Just over Make?
| Feature | Make | Just |
|---|---|---|
| Cross-platform | Requires GNU Make | Works consistently everywhere |
| PHONY declarations | Required for non-file targets | Not needed (all recipes are "phony") |
| Default recipe | Requires explicit default: |
First recipe or default |
| Help/listing | Manual implementation | Built-in just --list |
| Variables | Complex syntax $(VAR) |
Simple syntax {{var}} |
| Parameters | Awkward | Native support |
| String interpolation | Limited | Full support |
| Error messages | Cryptic | Clear and helpful |
| Dependencies | File-based | Recipe-based |
Installation
# macOS
brew install just
# Cargo (cross-platform)
cargo install just
# Other platforms: https://github.com/casey/just#installation
Core Principles
- Consistency: Common interface across all components regardless of underlying technology
- Simplicity: Hide platform-specific commands behind standard recipes
- Discoverability:
just --listshows all available commands with descriptions - Platform Independence: Works across different languages and toolchains
Standard Structure
Required Elements
Every justfile MUST have:
- Recipe comments using
#for--listoutput - Default recipe (first recipe or explicit
default) - Standard recipes for common operations
Template
# Show available recipes
default:
@just --list
# Set up and validate the local development environment
init:
./scripts/init.sh
# Install all dependencies
install:
npm install # or pip install -r requirements.txt, etc.
# Run in development mode (with live reload)
dev:
npm run dev # or python -m flask run, etc.
# Validate code formatting and linting
lint:
npm run lint # or ruff check, etc.
# Auto-fix linting issues
lint-fix:
npm run lint:fix # or ruff check --fix, etc.
# Run tests
test:
npm test # or pytest, etc.
# Run tests with coverage
test-coverage:
npm test -- --coverage # or pytest --cov, etc.
# Build the project for distribution
build:
npm run build # or go build, etc.
# Remove build artifacts and temporary files
clean:
rm -rf dist/ node_modules/.cache/
# Run all CI checks
ci: lint test build
@echo "CI checks passed"
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 · 572 lines · 14 tokens per session scan C 6fe8dee94224
150-justfile is a cursor rule published in the GitHub repository d-padmanabhan/agent-engineering-handbook (16 stars, last pushed 6d ago), licensed MIT. It adds 14 tokens to every session and 3,173 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.