A five-stage coding workflow that takes a feature listed in ROADMAP.md through research, design, implementation, testing, and review.

Use it with /ship, /ship next, or a roadmap feature request when building a feature in the FreeCAD project.

It gives each roadmap feature a defined sequence and project-specific completion requirements, reducing the need for every stage to rediscover them.

How maximedns5/freecad-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to maximedns5/freecad-mcp. 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/maximedns5/freecad-mcp/verified-cad-tools/.claude/skills/ship/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/maximedns5/freecad-mcp

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/maximedns5/freecad-mcp/ship/github.svg)](https://agentmods.dev/skills/maximedns5/freecad-mcp/ship)

Your own site

<a href="https://agentmods.dev/skills/maximedns5/freecad-mcp/ship"><img src="https://agentmods.dev/badge/skills/maximedns5/freecad-mcp/ship/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/maximedns5/freecad-mcp/ship"><img src="https://agentmods.dev/badge/skills/maximedns5/freecad-mcp/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 999 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.00050	$0.00999
Opus 5	$0.00025	$0.00500
Sonnet 5	$0.00010	$0.00200
Haiku 4.5	$0.00005	$0.00100

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

Security

Grade A, and why

ship 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 10d 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/ship/SKILL.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/ship — run a roadmap feature through the pipeline

Drive one feature from ROADMAP.md through the coding pipeline (researcher → architect → coder → tester → reviewer), with the project-specific definition of done injected so no stage has to rediscover it.

Resolve the feature

Read ROADMAP.md.
If the argument is a feature ID (e.g. colors-materials), use that entry. If the argument is next or empty, use the first entry with Status: ready.
Refuse (politely, explaining why) if the entry is later or done, or if a ready entry has a research track — in that case ship only its "shippable now" piece and say so.
Tell the user which feature is being shipped before spawning anything.

Compose the task prompt

Build one self-contained task prompt containing, in order:

The full roadmap entry, verbatim (intent, current state, design sketch, definition of done, verification).
This project definition of done, always:
- Four touch points for any new tool: RPC method in addon/FreeCADMCP/rpc_server/ (dispatched to the GUI thread via gui_dispatch), implementation in src/freecad_mcp/operations/core.py, tool declaration in src/freecad_mcp/server.py, entry in the README Tools list.
- Measured consequence: return values report measured state (properties read back, volumes, bounding boxes), never bare "success".
- Version skew: the MCP server must degrade gracefully when the addon is older and lacks the new RPC method (see place's fallback for the pattern).
- Tests within stub limits: unit tests only for pure logic per tests/conftest.py; do not stub more of the FreeCAD API to force testability.
- uv run ruff check . and uv run pytest must pass.
The reminder that final geometry verification runs against live FreeCAD and is manual: the reviewer's report must end with the exact commands/steps the user should run (addon redeploy + restart if addon/ changed, then what to exercise), not a claim that it was verified.

Read the full file on GitHub · 81 lines

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.

10d ago First seen · 81 lines · 50 tokens per session scan A d5ed7e2d96d2

Subscribe to this mod's changes

ship is a skill published in the GitHub repository maximedns5/freecad-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 999 once invoked, about $0.0003 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.

Planning Project management

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

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…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

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…

Donchitos/Claude-Code-Game-Studios · 77 tokens

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.

Orkas-AI/Orkas · 5 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens

freecad-mcp: Skill for Claude Code