Borrowing it
Nothing to install: this file belongs to GadatheGod/freecad-mcp-pro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GadatheGod/freecad-mcp-pro/main/.opencode/skills/f-to-tickets/SKILL.mdgit clone --depth 1 https://github.com/GadatheGod/freecad-mcp-proWrote 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/gadathegod/freecad-mcp-pro/f-to-tickets)<a href="https://agentmods.dev/skills/gadathegod/freecad-mcp-pro/f-to-tickets"><img src="https://agentmods.dev/badge/skills/gadathegod/freecad-mcp-pro/f-to-tickets/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/gadathegod/freecad-mcp-pro/f-to-tickets"><img src="https://agentmods.dev/badge/skills/gadathegod/freecad-mcp-pro/f-to-tickets.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.00022 | $0.00564 |
| Opus 5 | $0.00011 | $0.00282 |
| Sonnet 5 | $0.00004 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
f-to-tickets 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 12d 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
To Tickets — FreeCAD Edition
Break a FreeCAD design spec into tickets — each ticket creates one verifiable part/feature/analysis.
Context
- FreeCAD MCP at
/home/praveen/Desktop/Freecadmcp - Docs at
/home/praveen/Desktop/Freecadmcp/docs/freecad/
Process
1. Read the spec
Extract all parts, features, constraints, FEM setups, and drawings from the spec.
2. Break into vertical slices
Each ticket should create one complete, verifiable FreeCAD object or set of objects:
Ticket examples:
01-create-base-body— Create the base Part::Box or PartDesign body02-add-sketch-and-pad— Create sketch, apply Pad feature03-add-holes— Create circular holes with Draft::Circle or Part::Cylinder cutouts04-apply-fem-constraints— Add ConstraintFixed, ConstraintForce05-generate-mesh— Create FemMeshGmsh with proper size06-run-fem-analysis— Run CalculiX solver, verify results07-create-drawing— Generate TechDraw sheet with views
3. Define blocking edges
01-create-base-body → None
02-add-sketch → 01
03-add-features → 02
04-fem-constraints → 03
05-mesh → 04
06-fem-analysis → 05
07-drawing → 03
4. Quiz the user
Present the breakdown. Ask:
- Does the granularity feel right?
- Are the blocking edges correct?
- Should any tickets be merged or split?
5. Publish tickets
Write to /home/praveen/Desktop/Freecadmcp/.scratch/<feature-slug>/issues/<NN>-<slug>.md:
—
What to build: Create a FreeCAD object/feature that produces visible geometry.
Blocked by: the numbers/titles of tickets that gate this one.
FreeCAD MCP Commands:
create_documentif neededcreate_objectwith obj_type, obj_propertiesexecute_codefor complex operationsget_viewto verify
Acceptance criteria:
- Object created in FreeCAD
- Screenshot confirms correct geometry
- Dimensions match spec
- No errors in FreeCAD console
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.
- 12d ago First seen · 79 lines · 22 tokens per session scan A 1c449e2097a1
f-to-tickets is a skill published in the GitHub repository GadatheGod/freecad-mcp-pro (1 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 564 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…