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 agentmods add skills/jasperhartong/sketchup-code/package-pluginnpx skills add jasperhartong/sketchup-code --skill package-plugingit clone --depth 1 https://github.com/jasperhartong/sketchup-codeWhat 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 | $0.00041 | $0.00897 |
| Opus 5 | $0.00020 | $0.00449 |
| Sonnet 5 | $0.00008 | $0.00179 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade A, and why
package-plugin 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 3d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Package Plugin
Steps
-
Determine which plugin to package — default is
timmerman_skeleton_dimensionsunless the user specifies otherwise. Plugins:timmerman_skeleton_dimensions,timmerman_sketchup_bridge. -
Read the current version from the plugin's loader file:
- Skeleton Dimensions:
plugins/timmerman_skeleton_dimensions.rb— findEXTENSION.version = '...' - Bridge:
plugins/timmerman_sketchup_bridge.rb
- Skeleton Dimensions:
-
Bump the version — always bump before packaging (never repackage the same version):
- Patch bump by default (e.g.
1.0.0→1.0.1), unless the user specifies a minor or major bump. - Update the version string in the loader file using StrReplace.
- Patch bump by default (e.g.
-
Run the packager:
bash package.sh skeleton # or: bash package.sh bridge # or: bash package.sh (builds all) -
Update changelog — Each plugin has its own changelog:
- Skeleton Dimensions:
plugins/timmerman_skeleton_dimensions/CHANGELOG.md - Bridge:
plugins/timmerman_sketchup_bridge/CHANGELOG.md
Add an entry for the new version to the plugin's changelog. Follow Keep a Changelog format:
## [x.y.z]heading, then group changes under### Added,### Changed,### Fixed, or### Removedas appropriate. Focus on user-facing features only (what users see or get from the plugin), not internal refactors, dev tooling, or API docs. Place the new version at the top (below the header). - Skeleton Dimensions:
-
Tag and push — after committing the version bump and changelog, create a date-based release tag and push it so GitHub Actions builds the release:
today=$(date +%Y-%m-%d) last=$(git tag -l "release-${today}-*" | sort -t- -k4 -n | tail -1) n=$(( ${last##*-} + 1 )) # defaults to 1 if none exist git tag "release-${today}-${n}" git push origin main --tagsTags use the format
release-YYYY-MM-DD-N(e.g.release-2026-02-23-1). The count increments for multiple releases on the same day. The.github/workflows/release.ymlworkflow triggers onrelease-*tags, builds all plugin.rbzfiles, and attaches them to a GitHub Release.
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.
- 3d ago First seen · 60 lines · 41 tokens per session scan A 070e7b421727
package-plugin is a skill published in the GitHub repository jasperhartong/sketchup-code (5 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 897 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-31.
Other skills, from other repositories
particles
Use this skill when creating particle effects in Phaser 4. Covers ParticleEmitter, emission zones, death zones, particle properties, textures, gravity wells, and particle movement. Triggers on: particles, emitter, particle effect, explosion, fire, smoke.
web-games
Web browser game development principles. Framework selection, WebGPU, optimization, PWA.
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
ship-web-games
Package, deploy, and verify a playable Three.js or web game. Use for release builds, asset delivery, private/public deployment, production smoke tests, browser proof, release notes, rollback readiness, and cleanup of temporary QA resources.
unity
Compile, test, and drive Unity for this repo's C# packages (unity/core, jint, quickjs, clearscript) and the two Unity projects (tests/, kitchen-sink/). Use when a change touches C# under unity/, when Unity test results are needed, when a rendering snapshot has to be checked or regenerated, or when the app has to be…