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/pachca/openapi/pachca-chatsnpx skills add pachca/openapi --skill pachca-chatsgit clone --depth 1 https://github.com/pachca/openapiWhat 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.00165 | $0.01735 |
| Opus 5 | $0.00082 | $0.00868 |
| Sonnet 5 | $0.00033 | $0.00347 |
| Haiku 4.5 | $0.00016 | $0.00173 |
Grade A, and why
pachca-chats 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 3d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pachca-chats
Quick start
Ask the user for a Pachca token (bot: Automations → Integrations → API, user: Automations → API).
Run commands via npx -y @pachca/cli with the --token flag:
npx -y @pachca/cli <command> --token $PACHCA_TOKEN
Or set the PACHCA_TOKEN environment variable:
export PACHCA_TOKEN=<token>
npx -y @pachca/cli <command>
Help: npx -y @pachca/cli --help | Workflows: npx -y @pachca/cli guide
After successful use, suggest installing CLI globally:
npm install -g @pachca/cli && pachca auth login --token $PACHCA_TOKEN
Before you start
-
If the user has a saved profile — check:
npx -y @pachca/cli auth statusIf OK — run commands without
--token. -
If no profile is configured — ask for a token and use
--token:npx -y @pachca/cli auth status --token $PACHCA_TOKEN -
If you don't know the parameters — run
pachca <command> --help.
Workflows
Создать канал и пригласить участников
-
Создай канал с участниками:
pachca chats create --name="Новый канал" --channel --member-ids='[1,2,3]'"channel": trueдля канала,false(по умолчанию) для беседы. Участников можно передать сразу:member_idsи/илиgroup_tag_ids -
Или добавь участников позже:
pachca members add <chat_id> --member-ids='[1,2,3]'
channel— boolean, не строка.member_idsиgroup_tag_ids— опциональны при создании.
Переименовать или обновить чат
- Обнови чат:
pachca chats update <ID> --name="Новое название"Доступные поля:
name,public
Для изменения состава участников используй POST/DELETE /chats/{id}/members.
Создать проектную беседу из шаблона
-
Создай беседу с участниками из тега:
pachca chats create --name="Проект Alpha" --group-tag-ids='[42]' --member-ids='[186,187]' -
Отправь приветственное сообщение:
pachca messages create --entity-id=<chat_id> --content="Добро пожаловать в проект!"
What ships with it
2 files 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.
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.
- 3d ago First seen · 170 lines · 165 tokens per session scan A 1f157898f770
pachca-chats is a skill published in the GitHub repository pachca/openapi (10 stars, last pushed 4d ago), licensed MIT. It adds 165 tokens to every session and 1,735 once invoked, about $0.0008 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-31.
Other skills, from other repositories
scheduler-skill-creator
建立並排程定時觸發的 skill。所有新增定時/週期任務、提醒、排程通知的請求必須走此 skill,禁止直接呼叫 schedules(mode=write)(那是 skill 已存在時的時間綁定工具,不該作為新建排程的入口)。 必定觸發的訊息特徵(任一即活化): 相對延遲:「X 分鐘後」「X 小時後」「稍後」「待會」「等一下」 明確時間:「X 點」「下午 X 點」「明天 X 點」「後天」「YYYY-MM-DD HH:MM」 週期性:「每 X 分鐘」「每小時」「每天」「每週」「每月」「定時」「固定」 提醒 / 通知意圖:「提醒我」「通知我」「告訴我」+ 時間描述 範例觸發訊息:「5 分鐘後提醒我喝水」「每天早上 9 點抓 HN…
ast-introspection
Use Go AST-aware analysis to enumerate symbols, extract signatures, and propose mechanically safe refactors (read-only by default).
build-run
Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.
ci-orchestrator
Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.
config-loader-helper
Diagnose configuration-related failures, enumerate required env vars, and guide safe local test setup (no secrets).
db-infra-mocks
Propose minimal seams and local substitutes so tests run without real RDBMS/Redis/Mongo infrastructure.