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 skills add danielgap/openclaw-planitor --skill pipeline-validationgit clone --depth 1 https://github.com/danielgap/openclaw-planitorWrote 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/skills/danielgap/openclaw-planitor/pipeline-validation)<a href="https://agentmods.dev/skills/danielgap/openclaw-planitor/pipeline-validation"><img src="https://agentmods.dev/badge/skills/danielgap/openclaw-planitor/pipeline-validation/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/skills/danielgap/openclaw-planitor/pipeline-validation"><img src="https://agentmods.dev/badge/skills/danielgap/openclaw-planitor/pipeline-validation.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.00047 | $0.01749 |
| Opus 5.5 | $0.00019 | $0.00700 |
| Sonnet 5.5 | $0.00009 | $0.00350 |
| Haiku 4.5 | $0.00005 | $0.00175 |
Grade A, and why
pipeline-validation 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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline — FASE 1.5: Market Gate (Validation)
Quick sanity check: ¿Existe mercado para esta idea? Se ejecuta entre BRIEF y GROUND TRUTH para evitar gastar el pipeline completo en ideas que no pasan un filtro básico de viabilidad.
Cuándo se ejecuta
Después de FASE 1 (BRIEF). Antes de FASE 2 (GROUND TRUTH).
Input
| Fuente | Ruta |
|---|---|
| Brief del proyecto | projects/{proyecto}/BRIEF.json |
| Datos del usuario | Recopilados en fase BRIEF |
Output
| Producto | Ruta |
|---|---|
| Market Gate verdict | projects/{proyecto}/v{n}/MARKET-GATE.json |
Propósito
Evitar desperdiciar tokens y tiempo en ideas sin mercado validado. Un GO permite continuar el pipeline completo. Un NO-GO detiene el proceso y explica por qué.
Proceso
Paso 1: Quick Sanity Check
Evaluar si la idea tiene sentido básico de mercado:
- ¿Existe una categoría? ¿Este tipo de negocio existe en algún lugar del mundo?
- ¿Hay demanda demostrable? ¿La gente gasta dinero en algo similar?
- ¿El mercado es accesible? ¿Las barreras de entrada son razonables para el usuario?
Paso 2: Búsqueda de Competidores
Buscar mínimo 3 competidores o sustitutos:
| # | Tipo | Qué buscar |
|---|---|---|
| 1 | Competidor directo | Mismo producto/servicio, misma zona o zona comparable |
| 2 | Competidor directo | Alternativa 2 (otra ciudad, otro formato) |
| 3 | Competidor directo | Alternativa 3 |
| 4 | Benchmark internacional | Mejor caso global del sector (opcional pero recomendado) |
Método de búsqueda:
- Usar Investigación web:
"[tipo negocio] en [ciudad/región]" - Usar motor de búsqueda:
"[tipo negocio] [ciudad comparable]" - Google Maps para locales físicos
- Fuentes sectoriales si aplica
Para cada competidor encontrado:
- Nombre
- URL verificable
- Ubicación
- Público objetivo
- Rango de precios (si disponible)
- Modelo de negocio (suscripción, evento, sesión...)
Paso 3: Evaluación de Mercado Básica
Estimación rápida de tamaño de mercado:
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 · 181 lines · 47 tokens per session scan A 8cbbca8e738c
pipeline-validation is a skill published in the GitHub repository danielgap/openclaw-planitor (5 stars, last pushed 6mo ago), licensed MIT. It adds 47 tokens to every session and 1,749 once invoked, about $0.0002 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.