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 KevinInoCol/coppeliasim-mcp --skill project-structuregit clone --depth 1 https://github.com/KevinInoCol/coppeliasim-mcpWrote 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/kevininocol/coppeliasim-mcp/project-structure)<a href="https://agentmods.dev/skills/kevininocol/coppeliasim-mcp/project-structure"><img src="https://agentmods.dev/badge/skills/kevininocol/coppeliasim-mcp/project-structure/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/kevininocol/coppeliasim-mcp/project-structure"><img src="https://agentmods.dev/badge/skills/kevininocol/coppeliasim-mcp/project-structure.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.00077 | $0.01258 |
| Opus 5 | $0.00039 | $0.00629 |
| Sonnet 5 | $0.00015 | $0.00252 |
| Haiku 4.5 | $0.00008 | $0.00126 |
Grade A, and why
project-structure 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structure of a CoppeliaSim project
A CoppeliaSim project you can hand in, re-run and grade has a specific shape. This skill describes it. None of it is style: every piece solves a problem that shows up every time.
Before any code: what goes where
Anything that must be reproducible is written in Python against
coppeliasim_zmqremoteapi_client. That covers building the scene, assembling
the robot, and every control loop.
MCP tools are for looking and checking, not for building: list objects, read a position, fire a sensor, see whether the simulation is running. A control loop cannot fit through them, and forty walls is forty calls that leave no file behind.
Rule of thumb: if the result must survive closing CoppeliaSim, it goes in a script. If it is a question ("where did that wall end up?"), it goes in a tool.
One script per artifact
Do not put the scene, the robot and the controller in one file. They change at different rates: the scene is built once, the robot is tweaked twenty times, and the controller runs constantly.
scene.py the world: floor, walls, obstacles
robot.py the robot inside it: chassis, joints, sensors
control.py what the robot does: teleop, navigation, the task
Each runs on its own and leaves the scene in a known state.
The order of the functions
Scripts always follow the same sequence. Keeping it means anyone — including you a month from now — knows where to look.
def connect():
return RemoteAPIClient(host=COPPELIA_HOST, port=COPPELIA_PORT).require("sim")
def clean(sim):
"""Delete whatever the previous run left behind."""
def create_piece(sim, ...):
"""One function per kind of piece. Returns the handle."""
def build(sim):
"""Calls the create_* functions in order and returns what was built."""
def verify(...):
"""MEASURES the result. Does not assume it worked."""
def main():
sim = connect()
thing = build(sim)
ok = verify(thing)
if "--no-save" not in sys.argv:
sim.saveScene(SCENE_PATH)
print("\nVerdict:", "ready" if ok else "needs work")
if __name__ == "__main__":
main()
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 · 140 lines · 77 tokens per session scan A 56823a3337c5
project-structure is a skill published in the GitHub repository KevinInoCol/coppeliasim-mcp (0 stars, last pushed 14d ago), licensed MIT. It adds 77 tokens to every session and 1,258 once invoked, about $0.0004 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
tiaportal-mcp
A skill for controlling Siemens TIA Portal, the engineering software used to configure Siemens PLCs and HMIs. It works through an MCP server, a tool connection that lets an agent inspect and change projects.
asset-management
Manage ServiceNow hardware assets, software licenses, and lifecycle states on almhardware/almlicense — license allocation, CMDB-to-asset linking, warranty tracking, inventory aggregation (HAM/SAM).
kernelcad-assemblies
Multi-part assemblies — assembly(), parts, connectors, 7 mate types, fixed and revolute joints, .model()/.solvedModel(). Use for any model with two or more mechanical parts that need joint metadata.
kernelcad-kinematic
Use when verifying whether a moving assembly is buildable — sampled-pose collision sweeps across joint ranges, IK reachability for end-effector targets, mounting-hole fastener consistency, and static-load capacity on cantilever-shaped parts. Loads alongside kernelcad-authoring to gate design-time mechanism feasibility.
kernelcad-parts
Bundled parts catalog — discover, fetch, and mate standard fasteners, bearings, motors, headers, and connectors. Use whenever the model needs an off-the-shelf component instead of hand-modeled placeholder geometry.
use-the-available-kernel
Hard rules for which kernelCAD primitive to reach for when authoring from a reference photo. The from-reference loop fails most often because the author defaults to easy primitives and skips ones that exist. Read before writing any geometry.