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 ForgeCAD/forgecad-public-kit --skill forgecad-project-syncgit clone --depth 1 https://github.com/ForgeCAD/forgecad-public-kitWrote 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/forgecad/forgecad-public-kit/forgecad-project-sync)<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>- NVIDIA SkillSpector warn
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.
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.00033 | $0.00518 |
| Opus 5 | $0.00016 | $0.00259 |
| Sonnet 5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
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.
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 studiois for users and agents;forgecad devis only for developing ForgeCAD itself. - Login only for hosted commands.
forgecad loginbefore anyproject/publishcommand; local work (run, render, studio) needs no auth. - init creates, push syncs.
project init "Name"creates the remote project, writesforgecad.json, and pushes existing local files.pushonly syncs an already-initialized project.clone <slug>is the inverse: remote → new local folder. - Sync is content-hash based.
status/push/pullcompare file content hashes — no timestamps, no git; a file is "modified" purely by content difference. Loop: edit →project status→project push. - Sync vs single-file ops. Use
status/pull/pushfor normal sync; useproject file <read|save|delete|...>only for one hosted-file operation without a full push/pull cycle. - Project context required. All
project file *andpublishcommands must run inside a folder containingforgecad.json. - Shares are live references. A published model always shows the current project file, never a snapshot — pushing changes silently updates published models.
publishprints the share URL. - Non-interactive runs. Pass
--forceto skip confirmation prompts (push, pull, delete) in agent automation.
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.
- 8d ago First seen · 20 lines · 0 tokens per session scan A 43f34821dd0d
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.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.