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.
npx agentmods add skills/abm-dev-git/abm-mcp/abm-devnpx skills add abm-dev-git/abm-mcp --skill abm-devgit clone --depth 1 https://github.com/abm-dev-git/abm-mcpWhat 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 | $0.00067 | $0.02357 |
| Opus 5 | $0.00034 | $0.01179 |
| Sonnet 5 | $0.00013 | $0.00471 |
| Haiku 4.5 | $0.00007 | $0.00236 |
Grade A, and why
abm-dev 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 yesterday.
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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
abm.dev — B2B enrichment for agents
abm.dev turns an email, a name + company, or a LinkedIn URL into ~89 canonical fields per record (43 person + 46 company), each with a source citation and a confidence score, synthesised from ~10 data sources — and writes the results back to your CRM.
Connect
- MCP (preferred):
https://mcp.abm.dev/mcp— OAuth sign-in on first use. One-click from Claude: https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=abm.dev&connectorUrl=https%3A%2F%2Fmcp.abm.dev%2Fmcp - REST API:
https://api.abm.devwith theX-API-Keyheader — mint a key at https://abm.dev/settings/api-keys. Same verbs:POST /v2/enrich,POST /v2/search,POST /v2/source. - CLI:
npx -y @abmdev/cli@latest init --all -k <API_KEY>
The core loop (match → enrich → write back)
- Match the record in the CRM:
search_companies/search_contacts. Filters are EXACT-match — match ondomain/email, not display names ("Saffery" will not match "Saffery LLP"). No match?create_company/create_contact. - Enrich with the CRM id threaded through:
create_enrichment { type, input: { company_name, domain, crm_id } }→ returns ajob_id(async, commonly 3–8 min). Addrefresh: trueto force a from-scratch run when the record was enriched recently. Pollget_enrichmentevery 30–60s untilcompleted(a processing status with 0 fields is normal — do not give up before ~10 min), then read values withget_enrichment_fieldsand provenance withget_enrichment_sources. - Write back:
preview_writebackshows the per-field keep/use diff; thenapprove_enrichment(REAL CRM mutation). If the preview shows no/wrong matched record, passcrm_entity_idon approve.
Finding people (async search)
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.
- yesterday First seen · 138 lines · 67 tokens per session scan A 47ab19d9eca4
abm-dev is a skill published in the GitHub repository abm-dev-git/abm-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 2,357 once invoked, about $0.0003 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.
Other skills, from other repositories
deepline-ads-audiences
Use this skill when building, enriching, auditing, or uploading B2B paid ads audiences to Google Customer Match, Meta/Facebook Custom Audiences, or LinkedIn Matched Audiences. Triggers on phrases like '/deepline-ads-audience', '/deepline-ads-audiences', 'upload this audience', 'create custom audiences', 'personal…
deepline-gtm
GTM prospecting, enrichment, outreach, plays. Providers…
deepline-pre-research
Use when the user wants a last30days-style pre-research pass in Deepline: discover the critical public, private, CRM, workflow, social, and web data sources for a research/enrichment job; compare provider coverage; estimate Deepline credit cost; recommend the source plan before building or running the workflow; or…
deepline-analytics
Use this skill when answering business analytics, RevOps, GTM metric, pipeline, revenue, funnel, customer, or warehouse questions with Deepline. Triggers on phrases like 'query Snowflake', 'analyze pipeline', 'total ACV', 'break down by quarter', 'use the semantic layer', 'run a semantic query', or any use of…
niche-signal-discovery
Discover niche first-party signals that differentiate Closed Won vs Closed Lost accounts for ICP analysis. Use when the user provides won/lost customer domain lists and wants differential signals (website content, job listings, tech stack, maturity markers) to build account scoring models and prospecting criteria.…
deepline-engine
Build, publish, and verify a Deepline Play as a durable state machine over Customer DB tables, including a small paid pilot. Invoke this skill explicitly when the user asks to build an engine.