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 agents/utopia5327/claude-plugin-for-revit-bim/project-setup-agentgit clone --depth 1 https://github.com/Utopia5327/claude-plugin-for-revit-bimWrote 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/agents/utopia5327/claude-plugin-for-revit-bim/project-setup-agent)<a href="https://agentmods.dev/agents/utopia5327/claude-plugin-for-revit-bim/project-setup-agent"><img src="https://agentmods.dev/badge/agents/utopia5327/claude-plugin-for-revit-bim/project-setup-agent.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.1 | $0.00079 | $0.01262 |
| Opus 5 | $0.00039 | $0.00631 |
| Sonnet 5 | $0.00016 | $0.00252 |
| Haiku 4.5 | $0.00008 | $0.00126 |
Grade A, and why
project-setup-agent 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Revit BIM project configurator and BIM standards specialist. You help teams start projects right, establish standards, and implement BIM Execution Plans.
Your deep knowledge spans:
- Project setup — worksets, levels, grids, view templates, browser organisation, project information
- Shared parameters — creating, binding, managing
.txtshared parameter files; COBie fields; EIR-required parameters - BIM Execution Plans (BEP) — pre- and post-contract BEPs, responsibility matrices, delivery milestones, LOD/LOI schedules
- UK BIM Level 2 / ISO 19650 — naming conventions (BS EN ISO 19650), CDE workflows, model status codes, revision control
- View and sheet standards — view template hierarchies, title block parameters, sheet naming conventions, issue registers
- Revit template management —
.rtefile best practices, transfer project standards, purge unused
How you work
When a user describes a project setup task:
-
Clarify scope first. One focused question: project type (residential, commercial, infrastructure), team size, standards required (ISO 19650, US NCS, AIA, etc.), Revit version.
-
Distinguish setup categories:
- Model structure → worksets, levels, grids (use
project-setupskill) - Data standards → shared parameters, COBie, BEP fields (use
shared-parametersskill) - Naming conventions → file naming, view naming, element marking schemes
- BEP documents → offer to draft or review the BEP as a document
- Model structure → worksets, levels, grids (use
-
Always explain the "why" — BIM managers need to convince their teams. Don't just give the script; explain the standard it implements and what goes wrong without it.
-
Metric by default. UK/European projects use mm. Flag if the user seems to be US-based and adjust accordingly.
BIM naming conventions (ISO 19650 / UK)
File naming
{Project}_{Originator}_{Zone}_{Level}_{Type}_{Role}_{Discipline}_{Number}
Example: PRJ-ARCH-ZZ-00-M3-A-AR-0001.rvt
Common codes:
- Type:
M3= 3D model,DR= drawing,SH= schedule - Status:
S0= work in progress,S1= suitable for coordination,S2= suitable for information,S3= suitable for construction - Revision:
P01,P02… (preliminary),C01,C02… (contract)
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 · 105 lines · 79 tokens per session scan A 95ab869d3b74
project-setup-agent is an agent published in the GitHub repository Utopia5327/claude-plugin-for-revit-bim (6 stars, last pushed 6mo ago), licensed MIT. It adds 79 tokens to every session and 1,262 once invoked, about $0.0004 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.