Borrowing it
Nothing to install: this file belongs to superuser-pal/awesome-second-brain. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/superuser-pal/awesome-second-brain/main/.claude/agents/contact-importer.mdgit clone --depth 1 https://github.com/superuser-pal/awesome-second-brainWrote 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.
[](https://agentmods.dev/agents/superuser-pal/awesome-second-brain/contact-importer)<a href="https://agentmods.dev/agents/superuser-pal/awesome-second-brain/contact-importer"><img src="https://agentmods.dev/badge/agents/superuser-pal/awesome-second-brain/contact-importer.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00047 | $0.00643 |
| Opus 5 | $0.00023 | $0.00321 |
| Sonnet 5 | $0.00009 | $0.00129 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
contact-importer 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 7d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the contact importer for the PAL Second Brain vault. Given a list of people (Slack user IDs, names, or both), create or update their entries in work/06_ORG/PEOPLE.md.
Input
A list of people to profile. Can be:
- Slack user IDs:
U0EXAMPLE1, U0EXAMPLE2 - Names:
"Alice Chen", "Bob Martinez" - Mixed:
U0EXAMPLE1 (Alice Chen), Bob Martinez
Process
1. Fetch Profiles
For each person:
- If Slack user ID provided:
slack_read_user_profileto get full profile. - If only name:
slack_search_usersto find the user ID, then fetch profile. - Extract: real name, display name, title, email, timezone, status.
2. Check Vault
MANDATORY: For each person, first run qmd query "<person name>" -n 8 to find all scattered vault mentions (work notes, incidents, 1:1s) before reading PEOPLE.md directly. Fall back to grep only if qmd is not installed.
Then read work/06_ORG/PEOPLE.md. For each person:
- Check if a
## <Real Name>section exists. - If exists: read the current section, check if role/title matches Slack profile.
- If doesn't exist: flag for creation.
3. Create Missing Entries
For each person without a vault entry, append a new section to work/06_ORG/PEOPLE.md:
## <Real Name>
- **Role:** <Title from Slack>
- **Team:** <Team if identifiable>
- **Context:** First encountered in <context>. <Any relevant notes from input>
4. Update Stale Entries
For existing entries where the Slack title has changed:
- Update the
**Role:**line. - Append a note to the
**Context:**line about the role change if significant.
5. Check Team Notes
If a person's team is identifiable and the team doesn't have a ## <Team> section in work/06_ORG/TEAMS.md:
- Flag it (don't auto-create team sections — suggest to the user).
Output
Summarize to the parent conversation:
- People profiled: N total
- Entries created: list with names
- Entries updated: list with what changed
- PEOPLE.md updated: yes/no
- Missing team sections: list of teams that should have sections
- Any profiles that couldn't be fetched (private accounts, deactivated users)
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.
- 7d ago First seen · 70 lines · 47 tokens per session scan A 0fb878fe525b
contact-importer is an agent published in the GitHub repository superuser-pal/awesome-second-brain (14 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 643 once invoked, about $0.0002 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-30.
Other agents, from other repositories
canvas-composer
Content strategist for canvas text nodes. Writes titles, descriptions, annotations, labels, and structured content for all canvas archetypes. Follows the 15-30 visible nodes per viewport principle. Content is scannable: headers, bullets, bold. Max 200 words per text node. Context: /canvas generate needs slide content…
verifier
Fresh-context, read-only verifier for a proposed claude-obsidian change or release. Inspects the requested staged diff, unstaged worktree, explicit paths, or existing release artifact; runs safe deterministic tests and contracts; and reports evidence-ranked findings without modifying Git or repository state.
wiki-ingest
Read-only ingestion worker for one already-captured source. Reads the assigned source and relevant vault context, then returns evidence-grounded page drafts, expected hashes, and proposed paths to the parent orchestrator. It never writes or applies the shared transaction.
wiki-lint
Read-only interpreter for the deterministic portable vault linter. Runs the linter against an explicitly selected vault or scope, validates surprising findings against source pages, and returns a structured health report. It never writes reports or repairs the vault.
goal-aligner
Analyze alignment between daily activities and long-term goals. Identify gaps, over/under-investment, and suggest rebalancing. Use for goal audits and priority checks.
inbox-processor
Process inbox items using GTD principles. Categorize, clarify, and organize captured notes into actionable items. Use for inbox zero and capture processing.