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.
git clone --depth 1 https://github.com/crustdata/skillsWrote 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/rules/crustdata/skills/crustdata-tool-selection)<a href="https://agentmods.dev/rules/crustdata/skills/crustdata-tool-selection"><img src="https://agentmods.dev/badge/rules/crustdata/skills/crustdata-tool-selection/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.
<a href="https://agentmods.dev/rules/crustdata/skills/crustdata-tool-selection"><img src="https://agentmods.dev/badge/rules/crustdata/skills/crustdata-tool-selection.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.00718 |
| Opus 5 | $0.00018 | $0.00359 |
| Sonnet 5 | $0.00007 | $0.00144 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
crustdata-tool-selection 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.
What it actually says
The Crustdata MCP server is Code Mode. It exposes three tools — list_tools, get_schema, execute — and every data operation happens inside an execute script:
const r = await callTool('person_search', { filters, limit: 25 });
// r = { ok: true, data, credits_used } | { ok: false, status, errorType, message }
- Write plain JavaScript for
execute— any TypeScript syntax (: Type,as, generics) is a parse error that fails the whole run before anything is billed. - Call
get_schema(["<tool>"])before building filters — it returns filterable columns, value formats, and a response example. - A failed
callToolreturns{ ok: false, ... }; it does not throw. Checkokbefore usingdata.
Order of preference (cheapest correct path first):
- Company lookup:
company_identify(FREE) →company_enrichbycrustdata_company_id(2 credits per returned match; enriching by domain/name can fuzzy-match several companies and multiply the charge) - People search:
person_search(indexed DB, ~0.03 credits/result) → onlyperson_search_live(2 credits/result) when the DB returns 0 results or realtime data is required - Company search:
company_search(~0.03 credits/result) →company_search_live(2 credits/result) only for realtime - Contact info (emails/phones):
person_contact_enrichis THE tool — billed per contact type returned, no base fee, up to 25 profile URLs per call; narrowfields(e.g.contact.business_emails) to cap spend. Useperson_enrichonly for full profile data (work history, education, skills); itspreview: trueis free - Job listings:
job_search(filters/sorts/aggregations, ~0.03 credits/result) orjob_search_live(realtime scrape by company, 2 credits/result) - Social posts:
social_post_list_live(posts by one person or company) orsocial_post_search_live(LinkedIn keyword search); for X/Twitter or Reddit useweb_search_live - Web:
web_search_live(1 credit/query) andweb_enrich_live(fetch a page by URL, 1 credit/page) - Credits:
account_credits(FREE) for the balance; everycallToolresult carriescredits_usedfor the exact charge - Discover valid filter values:
company_autocomplete,person_autocomplete,job_autocomplete(FREE) - Bulk lists (thousands of rows): the async
batch_*twins (batch_person_enrich,batch_company_search, …) — submit, pollbatch_job_get, read viabatch_results - Alerts:
watch_create/watch_discovery_create(always preview withwatch_previewfirst — the server refuses an unpreviewed create)
list_tools returns the full annotated tool list with per-tool pricing; trust it over this summary when they disagree.
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 · 32 lines · 37 tokens per session scan A 7b345f68abb3
crustdata-tool-selection is a cursor rule published in the GitHub repository crustdata/skills (8 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 718 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-09-05.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.