build-abm
Skill4 starsChanged 6 days agoMITView on GitHub
Builds an agent-based model with ODD documentation, calibration, validation and experiment design.
In this repository210 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/ai-ml-code.mdcCursor rule
- .cursor/rules/code-translation.mdcCursor rule
- .cursor/rules/data-pipelines.mdcCursor rule
- .cursor/rules/documentation.mdcCursor rule
- .cursor/rules/dsge-code.mdcCursor rule
- .cursor/rules/econometrics-code.mdcCursor rule
- .cursor/rules/eviews-code.mdcCursor rule
- .cursor/rules/forecasts.mdcCursor rule
- .cursor/rules/gempack-code.mdcCursor rule
- .cursor/rules/lego-manifests.mdcCursor rule
- .cursor/rules/llm-code.mdcCursor rule
- .cursor/rules/model-code.mdcCursor rule
- .cursor/rules/notebooks-and-scripts.mdcCursor rule
- .cursor/rules/r-code.mdcCursor rule
- .cursor/rules/restricted-data.mdcCursor rule
- .cursor/rules/rl-code.mdcCursor rule
- .cursor/rules/sectoral-trade-climate-code.mdcCursor rule
- .cursor/rules/semi-structural-code.mdcCursor rule
- .cursor/rules/stata-code.mdcCursor rule
- .cursor/rules/tests.mdcCursor rule
- .cursor/rules/validation.mdcCursor rule
- adoptSkill
- ai-auditSkill
- backtestSkill
- build-causal-mlSkill
- build-cgeSkill
- build-climate-macroSkill
- build-deep-forecasterSkill
- build-drl-policySkill
- build-dsgeSkill
- build-financial-programmingSkill
- build-fpasSkill
- build-game-modelSkill
- build-hankSkill
- build-io-samSkill
- build-llm-agentsSkill
- build-llm-pipelineSkill
- build-multicountrySkill
- build-neural-solverSkill
- build-rag-kbSkill
- build-semi-structuralSkill
- build-sfcSkill
- build-trade-modelSkill
- calibrate-modelSkill
- calibration-planSkill
- carbon-pricing-analysisSkill
- chart-packSkill
- climate-scenarioSkill
- code-inventorySkill
- code-reviewSkill
- country-typologySkill
- create-exerciseSkill
- data-requirementsSkill
- debt-decompositionSkill
- debt-sustainabilitySkill
- design-trainingSkill
- distributional-analysisSkill
- equivalence-testSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.
- Very specific: line 27
Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …
- Distinctive: line 47
Document the model with the ODD protocol before coding
- Distinctive: line 58
Use common random numbers across policy variants
- Distinctive: line 64
After the ODD document: confirm agents, rules and protocols before coding
- Distinctive: line 65
After calibration: confirm targets and fit are adequate for the question
- Distinctive: line 66
Before policy experiments: confirm the experiment design and replications
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Generated from .claude/skills/build-abm/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->/build-abm — Build ABM
Category: Build · Primary agent: agent-based-modeling-specialist
Builds an agent-based model with ODD documentation, calibration, validation and experiment design.
Arguments: whatever the user wrote after the command name.
Purpose
Build an agent-based model whose aggregate behavior emerges from heterogeneous, boundedly rational agents interacting in markets and networks, documented well enough that someone else can rebuild it and calibrated tightly enough that its results are more than illustrations. The output is a reviewed, reproducible simulation model with a validation record, not a single striking simulation run.
Use it when heterogeneity, interaction, networks, disequilibrium or learning drive the question: financial contagion, housing booms, firm dynamics, distributional dynamics, or policy experiments where behavioral responses differ from rational-expectations benchmarks.
Do not use it when a representative-agent or heterogeneous-agent equilibrium model answers the question (/build-dsge, /build-hank), or when accounting consistency of sectoral balances is the main concern without agent heterogeneity (/build-sfc).
Before you start
- Check required inputs. For each input below record
FOUNDorABSENT(never 'assumed'):- Approved model-spec with agent rules
If a required input is
ABSENT, that part isNOT ASSESSED — NO DATA: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
- Approved model-spec with agent rules
If a required input is
- Check confidentiality. Identify the data classification level of the inputs (
.claude/docs/confidentiality-and-ai-use.md). Do not proceed with restricted or confidential data in a way the policy does not allow. - Collaboration. Follow
.claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and updateproduction/session-state/active.mdafter each approved section.
Agents
agent-based-modeling-specialist— primary agent; coordinates the work and integrates resultssimulation-based-inference-specialist— Estimates complex models with neural simulation-based inferencehpc-gpu-engineer— Engineers high-performance computing
Each agent is defined in .claude/agents/<name>.md. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. Subagents only write to the paths named in your instructions.
Key design decisions (present options, let the user choose)
| Decision | Typical options | What it changes |
| Agent types | households, firms, banks, government, foreign sector; number of each | Mechanisms available; runtime |
| Behavioral rules | fixed heuristics, adaptive learning, reinforcement learning, LLM-informed rules | Realism versus discipline; calibration burden |
| Market protocols | decentralized matching, search, posted prices, order books | Price formation and frictions |
| Accounting | full stock–flow consistency or partial | Credibility of aggregate dynamics |
| Calibration method | moment matching, indirect inference, simulation-based inference | Identification and uncertainty |
| Scale | hundreds to millions of agents | Statistical stability versus compute |
Workflow
- Document the model with the ODD protocol before coding
- Overview (purpose, entities, state variables, scales, process scheduling), Design concepts (emergence, adaptation, learning, interaction, stochasticity, observation) and Details (initialization, input data, submodels)
- State each behavioral rule with its evidence or rationale
- Implement with explicit random-seed management and unit tests for agent rules
- One generator per stochastic process; seeds recorded in every output
- Unit tests for each rule and for stock–flow consistency at the aggregate
- Calibrate by indirect inference or SBI; check stylized facts
- Targets: business-cycle moments, firm-size and income distributions, fat tails, volatility clustering, as relevant to the question
- Report fit to targeted and untargeted moments
- Design experiments and run with enough replications for stable estimates
- Determine replications from the convergence of Monte Carlo averages; report confidence bands
- Use common random numbers across policy variants
- Report sensitivity to parameters and seeds
- Global sensitivity analysis on behavioral parameters; key-driver ranking
- Register the model as a lego set (
/lego-map): a baseplate plus bricks with declared studs (variables, units, timing) and stubs, so components can later be attached, detached or swapped
Checkpoints with the user
- After the ODD document: confirm agents, rules and protocols before coding
- After calibration: confirm targets and fit are adequate for the question
- Before policy experiments: confirm the experiment design and replications
Common pitfalls
- Behavioral parameters tuned freely until the model delivers the expected result
- Results from a handful of runs
- Accounting leaks that create or destroy money or assets
- Undocumented code that reviewers cannot follow
Output
models/abm/<name>/ (+ model.lego.json)
The folder holds the ODD document, code, unit tests, calibration scripts and results, experiment scripts with seeds, the sensitivity report and the lego manifest. Every run saves its results to output/<run-id>/ in the model folder, with a run log (.claude/rules/model-code.md).
Gate / verdict
- ODD complete
- Stylized-facts validation and seed-robustness reported
- Lego manifest passes
python tools/lego.py check - Aggregate stock–flow consistency is verified by tests
- Confidence bands come from enough replications to be stable
Suggested next steps
/validate-model/policy-simulation/lego-map
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

