pachca-watch-thread

pachca-watch-thread is a skill for Claude Code, Codex from pachca/openapi. It costs 169 tokens per session (3,440 once invoked), scanned A, original, MIT.

A watcher for a Pachca conversation thread that reads new messages and replies while the session is open. Pachca is a team messaging service, and a thread is a message with its replies.

In plain words
What is it for?
It is for monitoring a specified thread, answering questions, asking colleagues for information, and keeping related work aligned with the discussion.
Why use it?
It lets an agent wait for responses and continue the conversation without requiring the user to check the thread manually.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code; mentions Codex.

Good fit It is for monitoring a specified thread, answering questions, asking colleagues for information, and keeping related work aligned with the discussion.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pachca/openapi/pachca-watch-thread
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 pachca/openapi --skill pachca-watch-thread
Clone the repo
git clone --depth 1 https://github.com/pachca/openapi

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 pachca-watch-thread

README.md
[![agentmods](https://agentmods.dev/badge/skills/pachca/openapi/pachca-watch-thread/github.svg)](https://agentmods.dev/skills/pachca/openapi/pachca-watch-thread)
Your own site
<a href="https://agentmods.dev/skills/pachca/openapi/pachca-watch-thread"><img src="https://agentmods.dev/badge/skills/pachca/openapi/pachca-watch-thread/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 pachca-watch-thread

Your own site · 80×15
<a href="https://agentmods.dev/skills/pachca/openapi/pachca-watch-thread"><img src="https://agentmods.dev/badge/skills/pachca/openapi/pachca-watch-thread.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 169 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,440 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.
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.00169 $0.03440
Opus 5.5 $0.00068 $0.01376
Sonnet 5.5 $0.00034 $0.00688
Haiku 4.5 $0.00017 $0.00344

Measured 4d ago against content hash d4ac4f1c6425, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pachca-watch-thread 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 4d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/watch.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

apps/docs/public/.well-known/skills/pachca-watch-thread/SKILL.md · 72 lines

How it starts

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

Watch a Pachca thread and reply

Watch the Pachca thread the user gave (a thread link, a message link or a thread id) and act on new messages within the goal they gave: answer questions, ask a colleague and wait for the answer, keep code or docs in step with the discussion. If there is no link but the goal names who to ask, offer to start a standalone thread with them, or a direct message if the user prefers one, and wait for a yes (step 1); with neither, ask for the link. If the goal is missing, ask for it in one line before you start. Start only when the user asks you to watch a thread or to wait for an answer in one: the watcher keeps running and replying on their behalf. A single reply is the pachca-messaging skill.

A background script does not get this program's MCP sign-in. So the watching runs through the Pachca CLI, and you read and reply with whichever you have, MCP tools or the CLI. The watcher is a process on the user's computer, so it runs where the program can start one (step 3). A chat in the Claude app, ChatGPT outside Codex and a cloud Claude Code session cannot: say so, offer to read the thread or reply once now and to check it again when asked, and for replies around the clock suggest a bot (the pachca-ai-agent skill). The guide for people is Агент следит за тредом.

1. Find the thread

Follow the pachca-search skill and its thread procedure, and note two numbers: the thread's id (for replies) and its chat_id (for reading and watching). For a thread id or a thread_id link, pachca_get_thread gives both. For a message link, use the "Find the thread chat" table in the skill's references/threads.md: a parent message carries both in thread, a comment inside a thread has the thread's chat_id as its own chat_id and the thread id as its entity_id. If the message has no thread yet, open one under it with pachca_create_thread, as «Подписаться на тред» in the message menu does (it returns the existing thread if one has appeared), and watch it. Like the button, opening posts nothing and notifies nobody: you, the message author, those who reacted and the chat members who turned on notifications about new threads become its members at once, and the chat members mentioned in the message follow a moment later, so your comments reach all of them. Write in it only when the goal calls for it, not to announce yourself, and tell the user that you opened it. If opening returns 403 without insufficient_scope, the chat is archived or the user is not its member (an open conversation or channel they only see): say so and offer another thread, or, in an open chat, joining it after a yes (pachca_add_members with their own id). Watch the message's chat itself only if the user asks for the chat, and warn that a busy chat wakes you more often. Read the whole thread to learn the context (pachca_list_chat_messages by the chat_id, every page): a thread is one topic, usually a few dozen messages. In a chat without an end, such as a direct chat, read only the latest page. Note the newest message id.

Read the full file on GitHub · 72 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 4d ago Changed d4ac4f1c6425
  2. 9d ago Changed 1e9b0e230ed3
  3. 15d ago First seen · 72 lines · 169 tokens per session scan A a3a7efea9a55

Subscribe to this mod's changes

pachca-watch-thread is a skill published in the GitHub repository pachca/openapi (11 stars, last pushed yesterday), licensed MIT. It adds 169 tokens to every session and 3,440 once invoked, about $0.0007 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-11-03.

Related

pachca-watch-thread compared with skills from other repositories

pachca-watch-thread next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
pachca-watch-threadpachca/openapiSkill11yesterdayMITA169Claude Code, Codex
zafiro-configniki914/zafiroSkill380todayMITA0Claude Code, Codex
extension-uploadagenvoy/AgenvoySkill6044d agoAGPL-3.0A63Claude Code, Codex
e2atokencanopy/e2aSkill2002d agoApache-2.0A64Claude Code
bookmarksepivip/SeekerClawSkill322todayMITA55Claude Code, Codex
reminderssepivip/SeekerClawSkill322todayMITA68Claude Code, Codex
todosepivip/SeekerClawSkill322todayMITA63Claude Code, Codex