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/juandoroteoflesiauni-lang/Market-options-stocks-ScannerWrote 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/juandoroteoflesiauni-lang/market-options-stocks-scanner/040-vibecoding-workflow)<a href="https://agentmods.dev/rules/juandoroteoflesiauni-lang/market-options-stocks-scanner/040-vibecoding-workflow"><img src="https://agentmods.dev/badge/rules/juandoroteoflesiauni-lang/market-options-stocks-scanner/040-vibecoding-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/juandoroteoflesiauni-lang/market-options-stocks-scanner/040-vibecoding-workflow"><img src="https://agentmods.dev/badge/rules/juandoroteoflesiauni-lang/market-options-stocks-scanner/040-vibecoding-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.01775 | $0.01775 |
| Opus 5 | $0.00888 | $0.00888 |
| Sonnet 5 | $0.00355 | $0.00355 |
| Haiku 4.5 | $0.00178 | $0.00178 |
Grade A, and why
040-vibecoding-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 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.
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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 VIBECODING WORKFLOW — TERMINAL DE TRADING
FILOSOFÍA: IA COMO DESARROLLADOR COMPLETO
El usuario no escribe código. La IA es el 100% del desarrollador. Esto requiere un proceso estructurado para evitar el caos del vibecoding.
📋 INICIO DE CADA SESIÓN
Al comenzar una nueva sesión de trabajo, la IA DEBE:
1. Leer PROJECT_CONFIG.md (estado actual del proyecto)
2. Preguntar: "¿En qué módulo trabajamos hoy?"
3. Confirmar la FASE (Blueprint / Construct / Validate)
4. Listar los archivos que se van a tocar
5. Estimar tiempo y complejidad
Template de inicio de sesión:
📊 RESUMEN DEL ESTADO ACTUAL:
- Módulo activo: [nombre]
- Fase: [Blueprint/Construct/Validate]
- Archivos afectados: [lista]
- Bloqueadores conocidos: [lista o "Ninguno"]
🎯 PLAN PARA ESTA SESIÓN:
1. [Tarea 1]
2. [Tarea 2]
3. [Tarea 3]
⚠️ RIESGOS: [lista o "Sin riesgos identificados"]
¿Procedemos con este plan? (Sí / Modificar plan)
🔵 FASE 1: BLUEPRINT (Planificación)
CUÁNDO: Antes de empezar cualquier módulo nuevo. REGLA: NADA de código en esta fase.
Qué producir en Blueprint:
# Blueprint: [Nombre del Módulo]
## Propósito
¿Qué problema resuelve este módulo?
## Interfaces (qué recibe y qué devuelve)
- Input: ...
- Output: ...
- Eventos que emite: ...
## Dependencias
- Módulos que necesita: ...
- APIs externas: ...
- Librerías nuevas: ...
## Estructura de archivos a crear/modificar
- [ ] backend/app/services/nuevo_servicio.py
- [ ] frontend/src/components/NuevoComponente.tsx
- [ ] tests/test_nuevo_servicio.py
## Casos borde a manejar
- ¿Qué pasa si la API externa falla?
- ¿Qué pasa si el usuario tiene fondos insuficientes?
- ¿Qué pasa si hay desconexión de internet?
## Estimación
- Archivos nuevos: X
- Archivos modificados: Y
- Complejidad: Baja / Media / Alta
🟡 FASE 2: CONSTRUCT (Construcción)
CUÁNDO: Después de que el Blueprint fue aprobado. REGLA: Un archivo a la vez. Mostrar antes de continuar.
Orden de construcción obligatorio:
1. Tipos/Schemas (types.ts / schemas.py)
2. Modelos de datos
3. Servicios/lógica de negocio
4. Repositorios (acceso a DB)
5. API endpoints (backend) / Hooks (frontend)
6. Componentes UI (frontend)
7. Tests
8. Documentación
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 · 268 lines · 1,775 tokens per session scan A 502270f6d68f
040-vibecoding-workflow is a cursor rule published in the GitHub repository juandoroteoflesiauni-lang/Market-options-stocks-Scanner (11 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 1,775 tokens to every session, about $0.0089 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
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.