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 corezoid/simulator-ai-plugin --skill commitgit clone --depth 1 https://github.com/corezoid/simulator-ai-pluginWrote 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/corezoid/simulator-ai-plugin/commit)<a href="https://agentmods.dev/skills/corezoid/simulator-ai-plugin/commit"><img src="https://agentmods.dev/badge/skills/corezoid/simulator-ai-plugin/commit/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/corezoid/simulator-ai-plugin/commit"><img src="https://agentmods.dev/badge/skills/corezoid/simulator-ai-plugin/commit.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.00049 | $0.00701 |
| Opus 5.5 | $0.00020 | $0.00280 |
| Sonnet 5.5 | $0.00010 | $0.00140 |
| Haiku 4.5 | $0.00005 | $0.00070 |
Grade A, and why
commit 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 1mo 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.
This is a copy
97% identical to commit — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit with auto version bump
This project follows semver. Every commit must include a version bump in:
plugins/corezoid/.claude-plugin/plugin.json.claude-plugin/marketplace.json
Step 1 — Inspect changes
Run in parallel:
git diff HEAD— see what changedgit status— see untracked filesgit log -5 --oneline— see recent commit style
Step 2 — Determine bump type
| Change type | Bump |
|---|---|
| New feature, new tool, new skill, new node type | minor (2.3.x → 2.4.0) |
| Bug fix, doc update, text fix, refactor | patch (2.3.x → 2.3.x+1) |
| Breaking change, major redesign | major (2.x.x → 3.0.0) |
Read current version from plugins/corezoid/.claude-plugin/plugin.json.
Step 3 — Update versions
Update the "version" field in both files to the new version:
plugins/corezoid/.claude-plugin/plugin.json.claude-plugin/marketplace.json
Step 3.5 — Update CHANGELOG.md
Prepend a new entry at the top of CHANGELOG.md (right after the # Changelog heading) following the existing format:
## [<new_version>]
- <bullet summarising what changed — one line per logical change>
Derive the bullets from the staged diff: group related changes into a single readable line each. Keep it concise — one sentence per item.
Step 3.6 — Update README.md
Review the diff for changes that affect README content and update the relevant sections in README.md:
| What changed | What to update in README.md |
|---|---|
New or removed skill (SKILL.md added/deleted) |
What it does table — add/remove the row |
| New or removed MCP tool | MCP Tools table — add/remove the row; Architecture code block if the tool group changes |
| New plugin directory or top-level file | Project structure code block |
| Breaking change to install/config | Installation or Configuration section |
If none of the above apply (e.g. pure bug fix, refactor, doc-only change inside an existing skill), skip this step — do not touch README.md.
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.
- 1mo ago First seen · 78 lines · 49 tokens per session scan A d1e85ae4954b
commit is a skill published in the GitHub repository corezoid/simulator-ai-plugin (60 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 701 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to commit, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
caveman-commit
Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.
git
Source-control safety for Git. Two rules apply whether or not you read the body. First, never commit, amend, push, tag, rebase, cherry-pick, revert, or reset --hard unless the user asked for that exact write in this session. An explicit request to create a new commit counts anywhere in the user's own task text, but it…
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
install-skill
Install a community skill pack into this fork from a GitHub repo and ship it as an auto-merged PR.