pachca-users

A Pachca administration tool for managing employees and tags, which are groups used to organise people in the workplace messaging service.

In plain words
What is it for?
Use it to list, create, update, block, or delete employees, change employee statuses, and manage or assign tags.
Why use it?
It gives an agent a defined way to inspect and change workspace membership and grouping information.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/pachca/openapi/pachca-users
Any agent
npx skills add pachca/openapi --skill pachca-users
Clone the repo
git clone --depth 1 https://github.com/pachca/openapi

Made for: Claude Code, Codex.

Per session 226 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,123 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00226 $0.02123
Opus 5 $0.00113 $0.01061
Sonnet 5 $0.00045 $0.00425
Haiku 4.5 $0.00023 $0.00212

Measured 2d ago against content hash 71fd3f3ece66, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

apps/docs/public/.well-known/skills/pachca-users/SKILL.md · 236 lines

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

  1. If the user has a saved profile — check:

    npx -y @pachca/cli auth status
    

    If OK — run commands without --token.

  2. If no profile is configured — ask for a token and use --token:

    npx -y @pachca/cli auth status --token $PACHCA_TOKEN
    
  3. If you don't know the parameters — run pachca <command> --help.

Workflows

Получить сотрудника по ID

  1. Получи информацию о сотруднике:
    pachca users get <ID>
    

Возвращает все поля, включая custom_properties, user_status, list_tags.

Массовое создание сотрудников с тегами

  1. Создай тег (если нужен):

    pachca group-tags create --name="Backend"
    
  2. Для каждого сотрудника: создай аккаунт с тегами:

    pachca users create --first-name="Иван" --last-name="Петров" --email="[email protected]" --list-tags='[{"name":"Backend"}]'
    

    Теги назначаются через поле list_tags в теле запроса

  3. Или обнови существующего:

    pachca users update <ID> --list-tags='[{"name":"Backend"}]'
    

Создание доступно только администраторам и владельцам (не ботам). Нет отдельного эндпоинта "добавить юзера в тег".

Создать гостя в чат

  1. Выбери активный чат, в который добавить гостя — узнай его ID:
    pachca chats list
    

    Чат должен быть активным (не архивным) и принадлежать вашей компании. У токена должно быть право добавлять в него участников.

Read the full file on GitHub · 236 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. 2d ago First seen · 236 lines · 226 tokens per session scan A 71fd3f3ece66

Subscribe to this mod's changes

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.