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-usersnpx skills add pachca/openapi --skill pachca-usersgit 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.00226 | $0.02123 |
| Opus 5 | $0.00113 | $0.01061 |
| Sonnet 5 | $0.00045 | $0.00425 |
| Haiku 4.5 | $0.00023 | $0.00212 |
Grade A, and why
pachca-users 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pachca-users
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
Получить сотрудника по ID
- Получи информацию о сотруднике:
pachca users get <ID>
Возвращает все поля, включая
custom_properties,user_status,list_tags.
Массовое создание сотрудников с тегами
-
Создай тег (если нужен):
pachca group-tags create --name="Backend" -
Для каждого сотрудника: создай аккаунт с тегами:
pachca users create --first-name="Иван" --last-name="Петров" --email="[email protected]" --list-tags='[{"name":"Backend"}]'Теги назначаются через поле
list_tagsв теле запроса -
Или обнови существующего:
pachca users update <ID> --list-tags='[{"name":"Backend"}]'
Создание доступно только администраторам и владельцам (не ботам). Нет отдельного эндпоинта "добавить юзера в тег".
Создать гостя в чат
- Выбери активный чат, в который добавить гостя — узнай его ID:
pachca chats listЧат должен быть активным (не архивным) и принадлежать вашей компании. У токена должно быть право добавлять в него участников.
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 · 236 lines · 226 tokens per session scan A 71fd3f3ece66
pachca-users is a skill published in the GitHub repository pachca/openapi (10 stars, last pushed 3d ago), licensed MIT. It adds 226 tokens to every session and 2,123 once invoked, about $0.0011 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
ast-introspection
Use Go AST-aware analysis to enumerate symbols, extract signatures, and propose mechanically safe refactors (read-only by default).
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.
build-run
Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.
code-navigation
Rapid, focused navigation to locate definitions/usages and map the impact of proposed changes.