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 agentmods add skills/danielgap/openclaw-planitor/document-writingnpx skills add danielgap/openclaw-planitor --skill document-writinggit clone --depth 1 https://github.com/danielgap/openclaw-planitorWhat 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 | $0.00000 | $0.00990 |
| Opus 5 | $0.00000 | $0.00495 |
| Sonnet 5 | $0.00000 | $0.00198 |
| Haiku 4.5 | $0.00000 | $0.00099 |
Grade A, and why
document-writing 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 2d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Writing Skill
Propósito
Redactar documentos profesionales de plan de negocio con estructura, claridad y rigor. Reemplaza la dependencia en un agente Redacción externo.
Principios de Redacción
1. Estilo
- Directo: Sin rodeos, sin "Great question!", sin relleno
- Data-driven: Cada afirmación respaldada por datos o fuente
- Profesional pero accesible: Un inversor debe entenderlo en 5 minutos
- Acción > explicación: Priorizar qué hacer sobre por qué
2. Estructura del Plan Final
# [Nombre del Proyecto] — Plan de Negocio v[N]
## Resumen Ejecutivo (1 página)
- Concepto en 2 frases
- Inversión necesaria
- Payback period
- Punto muerto
- Score del JUDGE
## 1. Concepto y Oportunidad
- Problema que resuelve
- Propuesta de valor única
- Por qué ahora
## 2. Mercado
- TAM / SAM / SOM (con fuentes)
- Tendencias del sector
- Segmentación de clientes
## 3. Competencia
- Mapa competitivo
- Ventaja competitiva sostenible
- Barreras de entrada
## 4. Modelo de Negocio
- Fuentes de ingreso
- Estructura de costes
- Pricing strategy
## 5. Plan Operativo
- Ubicación y local
- Equipo necesario
- Proveedores clave
- Timeline de lanzamiento
## 6. Proyecciones Financieras
- Escenario conservador / base / optimista
- Cash flow mensual (año 1)
- P&L proyectado (3 años)
- Break-even analysis
- Análisis de sensibilidad
## 7. Fiscalidad
- Régimen fiscal aplicable
- IVA, IRPF / IS, cuota autónomos
- Deducciones aplicables
- Obligaciones formales
## 8. Análisis DAFO
- Debilidades y Amenazas → planes de mitigación
- Fortalezas y Oportunidades → cómo explotarlas
## 9. Riesgos y Mitigación
- Kill criteria (cuándo parar)
- Plan B
- Stress tests
## 10. Conclusiones y Próximos Pasos
- Decisión: GO / NO-GO / CONDICIONAL
- Acciones inmediatas (primeras 4 semanas)
- Hitos clave a monitorizar
## Anexos
- A. Datos de mercado detallados
- B. Cálculos financieros
- C. Análisis de competencia expandido
- D. Fuentes consultadas
3. Formato y Tipografía
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.
- 2d ago First seen · 128 lines · 0 tokens per session scan A c91e52cf9d2e
document-writing is a skill published in the GitHub repository danielgap/openclaw-planitor (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 990 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…