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/datacommonsorg/agent-toolkit/data-commons-multi-entity-researchernpx skills add datacommonsorg/agent-toolkit --skill data-commons-multi-entity-researchergit clone --depth 1 https://github.com/datacommonsorg/agent-toolkitWrote 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/skills/datacommonsorg/agent-toolkit/data-commons-multi-entity-researcher)<a href="https://agentmods.dev/skills/datacommonsorg/agent-toolkit/data-commons-multi-entity-researcher"><img src="https://agentmods.dev/badge/skills/datacommonsorg/agent-toolkit/data-commons-multi-entity-researcher.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 | $0.00052 | $0.00885 |
| Opus 5 | $0.00026 | $0.00443 |
| Sonnet 5 | $0.00010 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade A, and why
data-commons-multi-entity-researcher 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 5d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Foundational Knowledge: Multi-Entity Graph Model
Data Commons models complex relationships between multiple entities using Multi-Entity Statistical Variables. Unlike standard single-entity variables that measure a property of one location (observationAbout), multi-entity variables track directed interactions, flows, or interactions between multiple entity roles (e.g., donor and recipient, exportingEntity and importingEntity, origin and destination).
1. The Three-Step Multi-Entity Tool Pipeline
When researching multi-entity relationship statistics, separate your work into three distinct phases:
- Discovery (
search_indicators): Find candidate variables for your concept (e.g., query"gross ODA aid"). Inspect the returnedobservation_propertieslist on each variable candidate (e.g.,["donor", "recipient"]). - Assessment (
get_variable_metadata): Pass candidate variables and entity DCIDs to verify dataset coverage, date ranges, provenances, and confirm the specificobservationProperties. - Retrieval (
get_multi_entity_observations): Fetch the observation tables using the mapped entity properties.
2. Parameter Configuration & Entity Property Mapping
A. Entity Mapping (entities dictionary - Required)
Map each entity property key (from observation_properties, e.g. "donor", "recipient") to its corresponding list of entity DCIDs:
- Direct Bilateral Pair:
"entities": { "donor": ["country/ARE"], "recipient": ["country/AFG"] }
B. Child Entity Expansion
To fetch observations across child places for a target property (e.g. UAE aid to all recipient countries):
- Set fixed DCIDs in
entitiesfor known roles (e.g."donor": ["country/ARE"]). - Set flat child expansion fields for the target property:
parent_entity_property:"recipient"parent_entity_dcid:"Earth"child_entity_type:"Country"
3. Playbook Recipes & Call Examples
Recipe 1: Direct Bilateral Pair (e.g., "Foreign aid from UAE to Afghanistan")
- Step 1 (Discovery):
search_indicators(query="official development assistance") - Step 2 (Assessment):
get_variable_metadata(variable_dcids=["Amount_EconomicActivity_GrossODA"], entity_dcids=["country/ARE", "country/AFG"]) - Step 3 (Retrieval):
get_multi_entity_observations(variable_dcid="Amount_EconomicActivity_GrossODA", entities={"donor": ["country/ARE"], "recipient": ["country/AFG"]})
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.
- 5d ago First seen · 65 lines · 52 tokens per session scan A 27656e571b30
data-commons-multi-entity-researcher is a skill published in the GitHub repository datacommonsorg/agent-toolkit (139 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 885 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…