forgecad-project-sync

forgecad-project-sync is a skill for Claude Code, Codex from ForgeCAD/forgecad-public-kit. It costs 33 tokens per session (518 once invoked), scanned A, original, MIT.

A command-line workflow for syncing local ForgeCAD project folders with forgecad.io, a hosted platform for storing, publishing, and sharing ForgeCAD projects.

In plain words
What is it for?
Use it to create or clone projects, synchronize files, manage members and shares, and run one live studio session for active projects.
Why use it?
It keeps local and hosted files connected and explains when to initialize, clone, pull, push, publish, or manage project access.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create or clone projects, synchronize files, manage members and shares, and run one live studio session for active projects.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/forgecad/forgecad-public-kit/forgecad-project-sync
Install

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.

Any agent
npx skills add ForgeCAD/forgecad-public-kit --skill forgecad-project-sync
Clone the repo
git clone --depth 1 https://github.com/ForgeCAD/forgecad-public-kit

Made for: Claude Code, Codex.

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 forgecad-project-sync

README.md
[![agentmods](https://agentmods.dev/badge/skills/forgecad/forgecad-public-kit/forgecad-project-sync.svg)](https://agentmods.dev/skills/forgecad/forgecad-public-kit/forgecad-project-sync)
Your own site
<a href="https://agentmods.dev/skills/forgecad/forgecad-public-kit/forgecad-project-sync"><img src="https://agentmods.dev/badge/skills/forgecad/forgecad-public-kit/forgecad-project-sync.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 518 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 19
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
Origin original 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.00033 $0.00518
Opus 5 $0.00016 $0.00259
Sonnet 5 $0.00007 $0.00104
Haiku 4.5 $0.00003 $0.00052

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

Security

Grade A, and why

forgecad-project-sync 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 8d 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.

skills/forgecad-project-sync/SKILL.md · 20 lines

What it actually says

Project Sync

forgecad.io is the hosted ForgeCAD platform; a project is a local folder linked to the server by forgecad.json. The full command inventory (project, file, member, share, token commands and flags) lives in forgecad project --help and the forgecad skill's docs/CLI.md — do not relearn it here.

  • One studio process. Run a single long-running forgecad studio <folder> [<folder> ...] naming every active project folder. The user opens the one printed localhost port once; create and edit files only under those folders so the browser live-updates. Never spawn extra servers per project.
  • studio vs dev. forgecad studio is for users and agents; forgecad dev is only for developing ForgeCAD itself.
  • Login only for hosted commands. forgecad login before any project/publish command; local work (run, render, studio) needs no auth.
  • init creates, push syncs. project init "Name" creates the remote project, writes forgecad.json, and pushes existing local files. push only syncs an already-initialized project. clone <slug> is the inverse: remote → new local folder.
  • Sync is content-hash based. status/push/pull compare file content hashes — no timestamps, no git; a file is "modified" purely by content difference. Loop: edit → project statusproject push.
  • Sync vs single-file ops. Use status/pull/push for normal sync; use project file <read|save|delete|...> only for one hosted-file operation without a full push/pull cycle.
  • Project context required. All project file * and publish commands must run inside a folder containing forgecad.json.
  • Shares are live references. A published model always shows the current project file, never a snapshot — pushing changes silently updates published models. publish prints the share URL.
  • Non-interactive runs. Pass --force to skip confirmation prompts (push, pull, delete) in agent automation.
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. 8d ago First seen · 20 lines · 0 tokens per session scan A 43f34821dd0d

Subscribe to this mod's changes

forgecad-project-sync is a skill published in the GitHub repository ForgeCAD/forgecad-public-kit (931 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 518 once invoked, about $0.0002 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.