contacts-lookup

contacts-lookup is a skill for Claude Code, Codex from Darwin-Agent/Car-bench-TRACE. It costs 161 tokens per session (2,953 once invoked), scanned C, original, MIT.

A contact lookup helper that finds the right person by name and returns details such as a phone number or email.

In plain words
What is it for?
Finding one or more contacts, resolving duplicate name matches, and retrieving contact information for calls, emails, or meeting attendees.
Why use it?
It avoids confusing people who share a name and keeps contact details separate from actions such as sending email or making a call.

Skill for Claude CodeCodex

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

Good fit Finding one or more contacts, resolving duplicate name matches, and retrieving contact information for calls, emails, or meeting attendees.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/darwin-agent/car-bench-trace/contacts-lookup
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 Darwin-Agent/Car-bench-TRACE --skill contacts-lookup
Clone the repo
git clone --depth 1 https://github.com/Darwin-Agent/Car-bench-TRACE

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-lookup

README.md
[![agentmods](https://agentmods.dev/badge/skills/darwin-agent/car-bench-trace/contacts-lookup/github.svg)](https://agentmods.dev/skills/darwin-agent/car-bench-trace/contacts-lookup)
Your own site
<a href="https://agentmods.dev/skills/darwin-agent/car-bench-trace/contacts-lookup"><img src="https://agentmods.dev/badge/skills/darwin-agent/car-bench-trace/contacts-lookup/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-lookup

Your own site · 80×15
<a href="https://agentmods.dev/skills/darwin-agent/car-bench-trace/contacts-lookup"><img src="https://agentmods.dev/badge/skills/darwin-agent/car-bench-trace/contacts-lookup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 161 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,953 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00161 $0.02953
Opus 5 $0.00081 $0.01477
Sonnet 5 $0.00032 $0.00591
Haiku 4.5 $0.00016 $0.00295

Measured 10d ago against content hash 37a5b0c841c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade C, and why

contacts-lookup scanned grade C with 1 finding 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 10d 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.

Tells the agent never to refusehighAnti-refusal

Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.

- **Once the person is settled, follow through — never refuse a capability you have.** After the user picks from the candidates (or the name resolved to one), you already hold that contact's id from the name search; go s
skills_bank/contacts-lookup/SKILL.md · 72 lines

How it starts

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

Look up contacts and fetch their details

The user wants a contact resolved and their details fetched — a phone number, an email, the info for several people. You find the contact id(s) by name, then fetch the detailed fields. A name may match several people, so the discipline is resolving the right person and reporting only what the tools return. This skill looks up contacts; sending an email is the send-email skill.

When this applies

"Look up ", "what's 's number/email?", "get me the contact info for everyone with last name ", "find the details for ." Often a precursor to an email (send-email) or a call (place-phone-call). Resolving a meeting attendee's details counts too — but there the ids usually come from the calendar, not a name search (see Method step 1).

Tools

  • get_contact_id_by_contact_name({contact_first_name | contact_last_name}) — find the contact id(s) matching a first or last name. Either field is optional, so you can search by first name alone, last name alone, or both. A name may match several people. Usually callable and returns names + ids, but verify it is in your tool set — if it is not, you cannot resolve anyone from a name at all (see below).
  • get_contact_information({contact_ids}) — fetch detailed fields (phone, email, …) for the given ids. This tool may not be callable for a given request — if so, only names + ids are obtainable, never phone/email. When it is callable, a returned field may still come back as the literal value "unknown"; treat that as genuinely unavailable (see below), never as a real value.
  • get_user_preferences({...email...}) — when the lookup is preparing an outgoing email, the user may have a learned preference to always copy a standing recipient (e.g. a secretary). Check the relevant preference category so you can offer that person; surface and confirm them rather than silently omitting or silently adding.
  • Verify before relying on any of these: only call what is actually in your tool set for this request, and read each result honestly rather than assuming it returned what you expected.

Read the full file on GitHub · 72 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. 10d ago First seen · 72 lines · 161 tokens per session scan C 37a5b0c841c1

Subscribe to this mod's changes

contacts-lookup is a skill published in the GitHub repository Darwin-Agent/Car-bench-TRACE (8 stars, last pushed 7d ago), licensed MIT. It adds 161 tokens to every session and 2,953 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.