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.
git clone --depth 1 https://github.com/madebyaris/poinf-of-salesWrote 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/madebyaris/poinf-of-sales/makefile-scripting)<a href="https://agentmods.dev/rules/madebyaris/poinf-of-sales/makefile-scripting"><img src="https://agentmods.dev/badge/rules/madebyaris/poinf-of-sales/makefile-scripting/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/rules/madebyaris/poinf-of-sales/makefile-scripting"><img src="https://agentmods.dev/badge/rules/madebyaris/poinf-of-sales/makefile-scripting.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.00000 | $0.02544 |
| Opus 5 | $0.00000 | $0.01272 |
| Sonnet 5 | $0.00000 | $0.00509 |
| Haiku 4.5 | $0.00000 | $0.00254 |
Grade C, and why
makefile-scripting 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 11d 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 "$TEMP_DIR" How it starts
The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Makefile & Shell Scripting Guidelines
Makefile Structure
Main Makefile Organization
Follow the patterns established in Makefile:
Standard Makefile Headers
# POS System - Development Makefile
# Usage: make <command>
.PHONY: help dev prod up down build logs clean backup restore create-admin remove-data db-shell test lint format
# Default target
.DEFAULT_GOAL := help
# Colors for output
GREEN := \033[0;32m
YELLOW := \033[0;33m
RED := \033[0;31m
BLUE := \033[0;34m
NC := \033[0m # No Color
Command Categories
Organize commands into logical groups:
- Development Commands - dev, prod, up, down, restart, build
- Database Commands - create-admin, remove-data, backup, restore, db-shell, db-reset
- Utility Commands - logs, status, clean, test, lint, format
- Quick Shortcuts - start, stop, install
Help System Pattern
## Help - Display available commands
help:
@echo "$(BLUE)POS System - Available Make Commands$(NC)"
@echo ""
@echo "$(GREEN)Development Commands:$(NC)"
@echo " make dev - Start development environment with hot reloading"
# ... more help text
Docker Integration
Docker Compose File Selection
# Docker compose files
COMPOSE_DEV := docker-compose.dev.yml
COMPOSE_PROD := docker-compose.yml
# Development environment
dev:
@docker compose -f $(COMPOSE_DEV) up --build
# Production environment
prod:
@docker compose -f $(COMPOSE_PROD) up -d --build
Container Management
# Check container status before operations
up:
@echo "$(GREEN)⬆️ Starting Docker containers...$(NC)"
@docker compose -f $(COMPOSE_DEV) up -d
@echo "$(GREEN)✅ Containers started in background$(NC)"
down:
@echo "$(YELLOW)⬇️ Stopping Docker containers...$(NC)"
@docker compose -f $(COMPOSE_DEV) down
@docker compose -f $(COMPOSE_PROD) down 2>/dev/null || true
@echo "$(GREEN)✅ Containers stopped$(NC)"
Shell Script Patterns
Script Structure
Follow the patterns from scripts/ directory:
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.
- 11d ago First seen · 348 lines · 0 tokens per session scan C 5d88f8b99496
makefile-scripting is a cursor rule published in the GitHub repository madebyaris/poinf-of-sales (142 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,544 tokens. 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
write
Writing style guide with AI detection avoidance. For tweets, LinkedIn, blogs, READMEs, commits. Activate with @write.
uv
This project is a uv workspace with multiple members (see pyproject.toml [tool.uv.workspace]).
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.
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.