contacts

contacts is a skill for Claude Code, Codex from yjwong/lark-cli. It costs 46 tokens per session (877 once invoked), scanned A, original, MIT.

A Lark contact lookup tool for finding information about employees and departments. Lark is a workplace collaboration platform.

In plain words
What is it for?
Use it to find users by name or ID, list people in a department, and look up job titles and department details.
Why use it?
It avoids manually searching an organization directory for a person's role, department, or contact record.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to find users by name or ID, list people in a department, and look up job titles and department details.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yjwong/lark-cli/contacts
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.

Any agent
npx skills add yjwong/lark-cli --skill contacts
Clone the repo
git clone --depth 1 https://github.com/yjwong/lark-cli

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for contacts

README.md
[![agentmods](https://agentmods.dev/badge/skills/yjwong/lark-cli/contacts/github.svg)](https://agentmods.dev/skills/yjwong/lark-cli/contacts)
Your own site
<a href="https://agentmods.dev/skills/yjwong/lark-cli/contacts"><img src="https://agentmods.dev/badge/skills/yjwong/lark-cli/contacts/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for contacts

Your own site · 80×15
<a href="https://agentmods.dev/skills/yjwong/lark-cli/contacts"><img src="https://agentmods.dev/badge/skills/yjwong/lark-cli/contacts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 877 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00046 $0.00877
Opus 5.5 $0.00018 $0.00351
Sonnet 5.5 $0.00009 $0.00175
Haiku 4.5 $0.00005 $0.00088

Measured 1mo ago against content hash 43e88d1e3b45, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

contacts 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 1mo 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.

skills/contacts/SKILL.md · 167 lines

How it starts

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

Contacts Lookup Skill

Look up employee information via the lark CLI.

Running Commands

Ensure lark is in your PATH, or use the full path to the binary. Set the config directory if not using the default:

lark contact <command>
# Or with explicit config:
LARK_CONFIG_DIR=/path/to/.lark lark contact <command>

Commands Reference

Get User by ID

# Look up by open_id (default)
lark contact get ou_xxxx

# Look up by user_id
lark contact get 12345 --id-type user_id

Output:

{
  "user_id": "ou_xxx",
  "open_id": "ou_xxx",
  "name": "Jane Doe",
  "en_name": "Jane Doe",
  "email": "[email protected]",
  "job_title": "Data Analyst",
  "department": "Business Intelligence"
}

List Users in Department

# List users in root department
lark contact list-dept

# List users in specific department
lark contact list-dept od_xxxx

Output:

{
  "contacts": [
    {
      "user_id": "ou_xxx",
      "name": "Alice",
      "job_title": "Engineer",
      "department": "Engineering"
    }
  ],
  "count": 1
}

Search Users by Name

lark contact search "Jane"
lark contact search "John Smith"

Output:

{
  "contacts": [
    {
      "user_id": "ou_xxx",
      "open_id": "ou_xxx",
      "name": "Jane Doe",
      "department": "Engineering"
    }
  ],
  "count": 1
}

Search Departments

lark contact search-dept "Engineering"

Output:

{
  "departments": [
    {
      "department_id": "od_xxx",
      "name": "Engineering",
      "member_count": 42
    }
  ],
  "count": 1
}

Integration with Calendar

When showing calendar events with attendees, you can enrich attendee info:

  1. Get attendee open_id from calendar event
  2. Use contact get <open_id> to fetch job title and department
  3. Present enriched attendee info to user

Example workflow:

# Get event with attendees
lark cal show <event_id>
# Returns attendees with open_id

# Look up each attendee
lark contact get ou_attendee_id
# Returns name, job_title, department

Read the full file on GitHub · 167 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. 1mo ago First seen · 167 lines · 46 tokens per session scan A 43e88d1e3b45

Subscribe to this mod's changes

contacts is a skill published in the GitHub repository yjwong/lark-cli (54 stars, last pushed 6mo ago), licensed MIT. It adds 46 tokens to every session and 877 once invoked, about $0.0002 per session on Opus 5.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-30.