agentmods.dev

pachca-security

A security audit-log tool for Pachca, a corporate messaging app, recording sign-ins, user actions, message changes, and data-loss-prevention events.

In plain words
What is it for?
Use it to review or export audit events, check login history, identify who performed an action, and investigate message or DLP incidents.
Why use it?
It helps trace what happened in the workspace and investigate suspicious activity or policy violations.

Skill for Claude CodeCodex

10 3d ago A scan 142 tokens copy · 86% MIT
View the source file pachca/openapi
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-security
Any agent
npx skills add pachca/openapi --skill pachca-security
Clone the repo
git clone --depth 1 https://github.com/pachca/openapi

Made for: Claude Code, Codex.

Per session 142 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,183 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 86% copy Near-identical to another mod 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.00142 $0.01183
Opus 5 $0.00071 $0.00592
Sonnet 5 $0.00028 $0.00237
Haiku 4.5 $0.00014 $0.00118

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

Security

Grade A, and why

pachca-security 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.

Origin

This is a copy

86% identical to pachca-oauth — 83 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.

apps/docs/public/.well-known/skills/pachca-security/SKILL.md · 120 lines

How it starts

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

pachca-security

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

Получить журнал аудита событий

  1. Получи журнал аудита: 
    pachca security list --start-time=<ISO-8601> --end-time=<ISO-8601>

    start_time и end_time обязательны (ISO-8601, UTC+0). Фильтры: event_key, actor_id, actor_type, entity_id, entity_type

Доступно только владельцу пространства.

Мониторинг подозрительных входов

  1. Получи события неудачных 2FA за период:

    pachca security list --start-time=<ISO-8601> --end-time=<ISO-8601> --event-key=user_2fa_fail --all

  2. Повтори запрос с --event-key=user_2fa_disabled — отключение второго фактора у сотрудника:

    pachca security list --start-time=<ISO-8601> --end-time=<ISO-8601> --event-key=user_2fa_disabled --all

  3. Если найдены аномалии — отправь уведомление администратору:

    pachca messages create --entity-type=user --entity-id=<admin_id> --content="Обнаружены подозрительные входы"

Экспорт логов за период

  1. Получи все события за период с пагинацией: 
    pachca security list --start-time=<ISO-8601> --end-time=<ISO-8601> --all

Read the full file on GitHub · 120 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 · 120 lines · 142 tokens per session scan A 6f90f928089b

Subscribe to this mod's changes

pachca-security is a skill published in the GitHub repository pachca/openapi (10 stars, last pushed 3d ago), licensed MIT. It adds 142 tokens to every session and 1,183 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to pachca-oauth, differing in 83 lines, and is treated as a copy.

Backend and APIsCode reviewLLMSecurityai-agentsapigokotlinmcp
Related

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).

pilinux/gorest · 28 tokens

ci-orchestrator

Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.

pilinux/gorest · 32 tokens

config-loader-helper

Diagnose configuration-related failures, enumerate required env vars, and guide safe local test setup (no secrets).

pilinux/gorest · 25 tokens

db-infra-mocks

Propose minimal seams and local substitutes so tests run without real RDBMS/Redis/Mongo infrastructure.

pilinux/gorest · 27 tokens

build-run

Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.

pilinux/gorest · 22 tokens

code-navigation

Rapid, focused navigation to locate definitions/usages and map the impact of proposed changes.

pilinux/gorest · 20 tokens