ponerme-al-dia-con-un-hilo

ponerme-al-dia-con-un-hilo is a skill for Claude Code, Codex from gethouston/houston. It costs 69 tokens per session (765 once invoked), scanned A, original, MIT.

A short summary of a long customer conversation that explains its current status, your promises, and what the customer is still waiting for. A thread is the complete sequence of messages in one conversation.

In plain words
What is it for?
Use it to catch up on inactive or lengthy support threads before writing the next response.
Why use it?
It saves you from rereading a long message history and reduces the chance of missing an unresolved commitment before replying.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to catch up on inactive or lengthy support threads before writing the next response.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gethouston/houston/ponerme-al-dia-con-un-hilo
Install

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.

Any agent
npx skills add gethouston/houston --skill ponerme-al-dia-con-un-hilo
Clone the repo
git clone --depth 1 https://github.com/gethouston/houston

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for ponerme-al-dia-con-un-hilo

README.md
[![agentmods](https://agentmods.dev/badge/skills/gethouston/houston/ponerme-al-dia-con-un-hilo/github.svg)](https://agentmods.dev/skills/gethouston/houston/ponerme-al-dia-con-un-hilo)
Your own site
<a href="https://agentmods.dev/skills/gethouston/houston/ponerme-al-dia-con-un-hilo"><img src="https://agentmods.dev/badge/skills/gethouston/houston/ponerme-al-dia-con-un-hilo/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.

agentmods 80×15 button for ponerme-al-dia-con-un-hilo

Your own site · 80×15
<a href="https://agentmods.dev/skills/gethouston/houston/ponerme-al-dia-con-un-hilo"><img src="https://agentmods.dev/badge/skills/gethouston/houston/ponerme-al-dia-con-un-hilo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 765 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00069 $0.00765
Opus 5 $0.00034 $0.00382
Sonnet 5 $0.00014 $0.00153
Haiku 4.5 $0.00007 $0.00076

Measured 9d ago against content hash 2d0c7aaa1aff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

ponerme-al-dia-con-un-hilo 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 9d 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.

store/agents-i18n/es/support/.agents/skills/ponerme-al-dia-con-un-hilo/SKILL.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ponerme al día con un hilo

Cuándo usarlo

conversations/{id}/thread.json tiene más de un puñado de mensajes y necesitas contexto rápido. Disparadores típicos:

  • Tú: "¿cómo va el hilo con Acme?"
  • Reabres una conversación inactiva por más de 3 días.
  • Antes de draft-a-reply en un hilo con 5 o más mensajes: ejecuta esto primero, la respuesta sale mejor.

Conexiones que necesito

Ejecuto el trabajo externo a través de Composio. Antes de que esta skill se ejecute, verifico que las categorías de abajo estén conectadas. Si falta alguna, nombro la categoría, te pido que la conectes desde la pestaña de Integraciones, y me detengo.

  • Bandeja de entrada (Gmail / Outlook): traigo el hilo en vivo si todavía no está en conversations.json. Opcional.
  • Mesa de ayuda (Intercom / Zendesk / Help Scout): fuente alterna del hilo. Opcional.

Si ninguna está conectada sigo trabajando con el índice local de hilos, pero te aviso que el resumen podría no incluir la respuesta más reciente.

Información que necesito

Primero leo tu contexto de soporte. Por cada campo obligatorio que falte, te hago UNA pregunta en lenguaje sencillo (mejor modalidad: app conectada > archivo > URL > texto pegado) y espero.

  • Qué hilo: Obligatorio. Por qué la necesito: resumo una conversación específica, no "soporte en general". Si falta, pregunto: "¿Cuál conversación resumo? Comparte el nombre del cliente o el asunto más reciente."
  • Audiencia del resumen: Opcional. Por qué la necesito: tres puntos para ti se leen distinto que un traspaso para un compañero de equipo. Si no la tienes, sigo con TBD y lo escribo pensando en que lo leas tú.

Pasos

  1. Cargar conversations/{id}/thread.json y la fila del índice en conversations.json.
  2. Recorrer el hilo cronológicamente. Anota: la petición original del cliente, cambios de alcance, cada promesa hecha, cada respuesta dada.
  3. Producir exactamente tres puntos:
    • Dónde estamos: último mensaje, quién lo envió, estado actual (esperando al cliente / esperando de nuestro lado / en borrador).
    • Qué prometimos: compromisos pendientes. Los tomo de followups.json filtrado por conversación, más promesas no capturadas en el hilo (recomiendo track-my-promises si encuentro alguna).
    • Qué espera el cliente ahora: la petición explícita o implícita más reciente.
  4. Añadir el resumen como bloque fechado en conversations/{id}/notes.md: queda guardado para la próxima vez.

Read the full file on GitHub · 49 lines

Changes

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.

  1. 9d ago First seen · 49 lines · 69 tokens per session scan A 2d0c7aaa1aff

Subscribe to this mod's changes

ponerme-al-dia-con-un-hilo is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 765 once invoked, about $0.0003 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-09-03.

Related

Other skills, from other repositories