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 skills add Utopia5327/claude-plugin-for-revit-bim --skill acc-design-collaborationgit 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/skills/utopia5327/claude-plugin-for-revit-bim/acc-design-collaboration)<a href="https://agentmods.dev/skills/utopia5327/claude-plugin-for-revit-bim/acc-design-collaboration"><img src="https://agentmods.dev/badge/skills/utopia5327/claude-plugin-for-revit-bim/acc-design-collaboration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/utopia5327/claude-plugin-for-revit-bim/acc-design-collaboration"><img src="https://agentmods.dev/badge/skills/utopia5327/claude-plugin-for-revit-bim/acc-design-collaboration.svg" alt="Reviewed on agentmods" width="80" 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.00179 | $0.02184 |
| Opus 5 | $0.00089 | $0.01092 |
| Sonnet 5 | $0.00036 | $0.00437 |
| Haiku 4.5 | $0.00018 | $0.00218 |
Grade A, and why
acc-design-collaboration 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 11d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ACC Design Collaboration — Revit Cloud Workflow
Set up and manage Design Collaboration for:
"$ARGUMENTS"
Overview
ACC Design Collaboration connects Revit teams working on cloud-hosted models. The workflow has two modes:
| Mode | When to use |
|---|---|
| Cloud Worksharing | Multiple Revit users on the same model simultaneously |
| Design Packages | Sharing a frozen snapshot of your model with other disciplines |
Part 1: Cloud Worksharing Setup (Revit UI — no API needed)
Step-by-step: Moving a local model to ACC
- Open the Revit model you want to migrate.
- Go to Collaborate tab → Collaborate button.
- Select "In BIM 360 / Autodesk Construction Cloud".
- Sign in with your Autodesk ID if prompted.
- Choose the ACC project and folder — place it in the Design Collaboration folder (usually
Project Files > [Discipline]). - Click OK — Revit saves the model to ACC and creates a local cache file.
- All team members open the model from ACC using Open → BIM 360 / ACC in Revit.
Workset best practices for cloud models
- Keep "Shared Levels and Grids" on its own workset — other disciplines will borrow from it.
- Each discipline should own one workset (Architecture, Structure, MEP, etc.)
- All team members should Synchronize with Central (SWC) at start and end of each session.
- Use Relinquish All Mine before closing.
- Never use Save As on a cloud model — it detaches from the cloud.
Who should use Cloud Worksharing?
- Same discipline, multiple users (e.g. 3 architects in the same Revit model)
- Teams working concurrently with live updates
Part 2: Design Packages — Sharing with other disciplines
Design Packages let you send a frozen snapshot of your model to other teams for reference.
Create a Design Package (Revit UI)
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.
- 11d ago First seen · 238 lines · 179 tokens per session scan A 436a7dedd288
acc-design-collaboration is a skill published in the GitHub repository Utopia5327/claude-plugin-for-revit-bim (6 stars, last pushed 6mo ago), licensed MIT. It adds 179 tokens to every session and 2,184 once invoked, about $0.0009 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.