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/jazzmind/busiboxWrote 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/jazzmind/busibox/specify-rules)<a href="https://agentmods.dev/rules/jazzmind/busibox/specify-rules"><img src="https://agentmods.dev/badge/rules/jazzmind/busibox/specify-rules/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/jazzmind/busibox/specify-rules"><img src="https://agentmods.dev/badge/rules/jazzmind/busibox/specify-rules.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.00608 | $0.00608 |
| Opus 5.5 | $0.00243 | $0.00243 |
| Sonnet 5.5 | $0.00122 | $0.00122 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
specify-rules 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 2mo 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.
What it actually says
busibox Development Guidelines
Auto-generated from all feature plans. Last updated: 2025-10-14
Active Technologies
- (001-create-an-initial)
- Bash 5.x (scripts), Ansible 2.14+ (configuration management), NGINX 1.18+ (reverse proxy) (002-deploy-app-servers)
- Python 3.11+ + FastAPI 0.104+, pymilvus 2.6+ (BM25 function support), redis-py 5.0+, boto3 (MinIO S3), psycopg 3.1+ (PostgreSQL async) (004-updated-data-service)
- PostgreSQL 15+ (metadata, status), Milvus 2.6+ (vectors with BM25), MinIO (S3-compatible file storage), Redis 7.0+ (Streams for job queue) (004-updated-data-service)
- Python 3.11+ + FastAPI 0.115+, Pydantic AI 0.0.20+, SQLAlchemy 2.0+ (async), asyncpg, APScheduler 3.10+, python-jose (JWT), httpx, OpenTelemetry SDK, sse-starlette (005-i-want-to)
- PostgreSQL 15+ (agent definitions, runs, tokens, workflows, scorers) (005-i-want-to)
- Python 3.11+ (existing agent-server stack) + FastAPI, SQLAlchemy, Pydantic, LiteLLM, APScheduler (all already integrated) (006-busibox-agents-specs)
- PostgreSQL 15+ with existing schema (agent_definitions, tool_definitions, workflow_definitions, eval_definitions, scheduled_runs, run_records) (006-busibox-agents-specs)
Project Structure
src/
tests/
Commands
Add commands for
Code Style
: Follow standard conventions
Recent Changes
- 006-busibox-agents-specs: Added Python 3.11+ (existing agent-server stack) + FastAPI, SQLAlchemy, Pydantic, LiteLLM, APScheduler (all already integrated)
- 005-i-want-to: Added Python 3.11+ + FastAPI 0.115+, Pydantic AI 0.0.20+, SQLAlchemy 2.0+ (async), asyncpg, APScheduler 3.10+, python-jose (JWT), httpx, OpenTelemetry SDK, sse-starlette
- 004-updated-data-service: Added Python 3.11+ + FastAPI 0.104+, pymilvus 2.6+ (BM25 function support), redis-py 5.0+, boto3 (MinIO S3), psycopg 3.1+ (PostgreSQL async)
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.
- 2mo ago First seen · 34 lines · 608 tokens per session scan A 702d84f53714
specify-rules is a cursor rule published in the GitHub repository jazzmind/busibox (7 stars, last pushed 1mo ago), licensed MIT. It adds 608 tokens to every session, about $0.0024 per session on Opus 5.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 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.
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.
family-instance-domain-actions
Family instance domain action implementation patterns.