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 commands/demolinator/revit-mcp-plugin/create-elementgit clone --depth 1 https://github.com/Demolinator/revit-mcp-pluginWhat 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.00010 | $0.00793 |
| Opus 5 | $0.00005 | $0.00396 |
| Sonnet 5 | $0.00002 | $0.00159 |
| Haiku 4.5 | $0.00001 | $0.00079 |
Grade A, and why
create-element 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 2d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a specific BIM element in Revit from a natural-language description.
Parse the Description
Extract from $ARGUMENTS:
- Element type: wall, column, beam, door, window, floor, roof, ceiling, level, grid, sheet, schedule
- Dimensions: length, width, height (convert to mm)
- Position: coordinates, grid references, relative positions ("at grid A1", "on the north wall")
- Level: which floor/level
- Material/type: concrete, brick, steel, glass, generic
Select the Right Tool
| Element | Tool | Key |
|---|---|---|
| Wall, beam (line-based) | create_line_based_element |
Needs start_point and end_point |
| Beam (structural) | create_structural_framing |
Needs start_point and end_point |
| Column, door, window, furniture | place_family |
Needs a single location point |
| Floor, roof, ceiling | create_surface_based_element |
Needs a closed boundary polygon |
| Level | create_level |
Needs elevation and optional name |
| Grid line | create_grid |
Needs start_point and end_point |
| Drawing sheet | create_sheet |
Needs sheet_number and sheet_name |
| Schedule | create_schedule |
Needs category and optional fields |
Find the Family Type
Call list_families to find a matching type.
Match the user's description to the closest available type:
- "concrete wall" -> look for types containing "Concrete" in the name
- "brick exterior" -> look for types containing "Brick" or "Exterior"
- "steel column" -> look for structural column types containing "Steel"
- If no exact match, use the first available type and tell the user what was used
Build the Parameters
- Convert all dimensions to mm
- Set coordinates based on the user's description
- If coordinates are ambiguous, call
get_current_view_infofor context, then ask the user - Set
level_namebased on the specified level - Use standard defaults for unspecified values:
- Wall height: 3000 mm
- Door: 900 x 2100 mm
- Window: 1200 x 1500 mm
- Floor-to-floor: 3000 mm (residential), 4000 mm (commercial)
- Column: height = floor-to-floor
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.
- 2d ago First seen · 64 lines · 10 tokens per session scan A eca8ac6c81ea
create-element is a command published in the GitHub repository Demolinator/revit-mcp-plugin (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 793 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.