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/development-workflow)<a href="https://agentmods.dev/rules/madebyaris/poinf-of-sales/development-workflow"><img src="https://agentmods.dev/badge/rules/madebyaris/poinf-of-sales/development-workflow/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/development-workflow"><img src="https://agentmods.dev/badge/rules/madebyaris/poinf-of-sales/development-workflow.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.00009 | $0.01470 |
| Opus 5 | $0.00005 | $0.00735 |
| Sonnet 5 | $0.00002 | $0.00294 |
| Haiku 4.5 | $0.00001 | $0.00147 |
Grade A, and why
development-workflow 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 13d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Workflow Guide
Quick Start Commands
Primary Development Workflow
Use Makefile for all development operations:
# Essential commands for daily development
make help # Show all available commands
make dev # Start development environment with hot reloading
make up # Start Docker containers in background
make down # Stop all containers
make status # Check system status
Database Management Workflow
# Database operations (all interactive and safe)
make create-admin # Create super admin user
make backup # Backup entire system (database + files)
make restore # Restore from backup (interactive menu)
make db-reset # Reset to fresh state with seed data
make db-shell # Access PostgreSQL shell
make remove-data # DESTRUCTIVE: Remove all data (multiple confirmations)
Development Environment Setup
First Time Setup
- Clone repository and navigate to project root
- Ensure Docker Desktop is running
- Run
make dev- automatically creates.envfile if missing - Access applications:
- Frontend: http://localhost:3000
- Backend API: http://localhost:8080
- Database: localhost:5432
Daily Development Workflow
# Start development session
make dev # Starts all services with hot reloading
# During development
make logs # View all service logs
make logs-backend # View only backend logs
make logs-frontend# View only frontend logs
# End development session
make down # Stop all containers
Database Development Workflow
Working with Database
- Fresh Start:
make db-reset- Clean database with seed data - Backup Before Changes:
make backup- Create safety backup - Make Changes: Edit schema files or use application
- Test Changes: Verify functionality
- Create Admin:
make create-admin- Add admin users as needed
Database Schema Changes
- Edit database/init/01_schema.sql
- Edit database/init/02_seed_data.sql if needed
- Run
make db-resetto apply changes - Test with fresh data
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.
- 13d ago First seen · 202 lines · 9 tokens per session scan A 733c7f430c23
development-workflow is a cursor rule published in the GitHub repository madebyaris/poinf-of-sales (142 stars, last pushed 1y ago), licensed MIT. It adds 9 tokens to every session and 1,470 once invoked, about $0.0000 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-30.
Other cursor rules, from other repositories
write
Writing style guide with AI detection avoidance. For tweets, LinkedIn, blogs, READMEs, commits. Activate with @write.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.
uv
This project is a uv workspace with multiple members (see pyproject.toml [tool.uv.workspace]).
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.