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/query-modelgit 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.00008 | $0.00754 |
| Opus 5 | $0.00004 | $0.00377 |
| Sonnet 5 | $0.00002 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
query-model 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.
What it actually says
Query the current Revit model and present results in clear, readable tables.
Determine Query Type
Based on $ARGUMENTS, determine what the user wants:
"status" / "connection" / no arguments:
- Call
get_revit_statusto check connection - Present: Revit version, project name, connection status
"model info" / "project":
- Call
get_revit_model_info - Present: project details, location, settings
"view info" / "current view":
- Call
get_current_view_info - Present: view name, type, scale, level
"views" / "all views":
- Call
list_revit_views - Present: list of views by type
"levels" / "floors":
- Call
list_levels - Present: level names, elevations
"walls" / "doors" / "windows" / any element category:
- Call
ai_element_filterwith the appropriate category (OST_Walls, OST_Doors, OST_Windows, etc.) - Present results in a table: ID, Type, Level, Key Parameters
"types" / "available types" / "family types":
- Call
list_familiesand/orlist_family_categories - Present: Family Name, Type Name, Category
"selected" / "selection":
- Call
get_selected_elements - Present details of selected elements
"stats" / "summary" / "overview" / "model statistics":
- Call
analyze_model_statistics - Present a summary table with element counts per category and totals
"rooms" / "room data" / "areas":
- Call
export_room_data - Present: Room Name, Number, Level, Area (sq m), Perimeter
"materials" / "quantities" / "takeoff":
- Call
get_material_quantities - Present: Material Name, Area (sq m), Volume (cu m), Element Count
"color" / "visualize":
- Ask what category and parameter to color by
- Call
color_splash
"clear colors" / "reset colors":
- Call
clear_colors
Output Format
Present all results in markdown tables. Keep it concise. Highlight key numbers (total count, total area).
If the query returns many elements, summarize by type and show the first 20 with a note about the total count.
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 · 69 lines · 8 tokens per session scan A 93bbd052861b
query-model is a command published in the GitHub repository Demolinator/revit-mcp-plugin (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 754 once invoked, about $0.0000 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
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.