REVIT_MCP_study: Skill for Claude Code

.claude/skills/core-reload-dev/SKILL.md

core-reload-dev is a skill for Claude Code from shuotao/REVIT_MCP_study. It costs 104 tokens per session (1,230 once invoked), scanned A, original, no licence file.

An opt-in development workflow for hot-reloading the RevitMCP core while Autodesk Revit stays open. It rebuilds, deploys, reloads, and checks the CoreRuntime.

In plain words
What is it for?
Testing core changes during RevitMCP development when the requested change supports the hot-reload branch.
Why use it?
It removes repeated Revit restarts while developers iterate on changes to components such as CommandExecutor.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

This is shuotao/REVIT_MCP_study's own configuration. It tells Claude Code how to work on REVIT_MCP_study itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything REVIT_MCP_study configures →

Reuse

Borrowing it

Nothing to install: this file belongs to shuotao/REVIT_MCP_study. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/shuotao/REVIT_MCP_study/main/.claude/skills/core-reload-dev/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/shuotao/REVIT_MCP_study

Made for: Claude Code.

Wrote 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.

agentmods badge for core-reload-dev

README.md
[![agentmods](https://agentmods.dev/badge/skills/shuotao/revit_mcp_study/core-reload-dev.svg)](https://agentmods.dev/skills/shuotao/revit_mcp_study/core-reload-dev)
Your own site
<a href="https://agentmods.dev/skills/shuotao/revit_mcp_study/core-reload-dev"><img src="https://agentmods.dev/badge/skills/shuotao/revit_mcp_study/core-reload-dev.svg" alt="Measured on agentmods" height="20"></a>
Per session 104 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,230 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00104 $0.01230
Opus 5 $0.00052 $0.00615
Sonnet 5 $0.00021 $0.00246
Haiku 4.5 $0.00010 $0.00123

Measured 7d ago against content hash 5c180951a9f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

core-reload-dev 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 7d 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.

.claude/skills/core-reload-dev/SKILL.md · 56 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 7d ago First seen · 56 lines · 104 tokens per session scan A 5c180951a9f9

Subscribe to this mod's changes

core-reload-dev is a skill published in the GitHub repository shuotao/REVIT_MCP_study (103 stars, last pushed 6d ago), with no licence file. It adds 104 tokens to every session and 1,230 once invoked, about $0.0005 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-30.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens