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-tasksnpx skills add pachca/openapi --skill pachca-tasksgit 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.00169 | $0.01378 |
| Opus 5 | $0.00084 | $0.00689 |
| Sonnet 5 | $0.00034 | $0.00276 |
| Haiku 4.5 | $0.00017 | $0.00138 |
Grade A, and why
pachca-tasks 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.
This is a copy
86% identical to pachca-oauth — 113 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pachca-tasks
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 tasks create --kind=reminder --content="Позвонить клиенту" --due-at=<дата> --chat-id=<chat_id>chat_idдля привязки к чату,custom_propertiesдля дополнительных полей
Тип
custom_properties[].valueвсегда строка. Дополнительные поля: GET /custom_properties?entity_type=Task.
Получить список предстоящих задач
- Получи невыполненные задачи:
pachca tasks list --status=undone --allstatus:"undone"— не выполнена,"done"— выполнена. Без параметра возвращаются задачи в любом состоянии. Ещё фильтры:--author-id,--performer-ids,--chat-ids
Собрать задачи по чатам проекта
-
Запроси задачи нужных чатов:
pachca tasks list --chat-ids=198,334 --allС
--chat-idsвыдача перестаёт ограничиваться своими задачами и отдаёт все задачи указанных чатов. Недоступные чаты игнорируются без ошибки, не более 100 идентификаторов -
Сузь выборку по автору, ответственным и состоянию:
pachca tasks list --chat-ids=198,334 --author-id=12 --performer-ids=185,186 --status=undone --allФильтры комбинируются между собой
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 · 150 lines · 169 tokens per session scan A 9c99796a1778
pachca-tasks is a skill published in the GitHub repository pachca/openapi (10 stars, last pushed 4d ago), licensed MIT. It adds 169 tokens to every session and 1,378 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to pachca-oauth, differing in 113 lines, and is treated as a copy.
Other skills, from other repositories
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.
migration-helper
Analyze GORM model changes, estimate resulting schema (DDL) differences, and propose safe migration steps with verification guidance.