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/evolvinglmms-lab/llava-onevision-2/commit-messagenpx skills add EvolvingLMMs-Lab/LLaVA-OneVision-2 --skill commit-messagegit clone --depth 1 https://github.com/EvolvingLMMs-Lab/LLaVA-OneVision-2What 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.00017 | $0.01879 |
| Opus 5 | $0.00009 | $0.00940 |
| Sonnet 5 | $0.00003 | $0.00376 |
| Haiku 4.5 | $0.00002 | $0.00188 |
Grade A, and why
commit-message 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 2d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Use this skill when writing git commit messages. It enforces a formal Conventional Commits style suitable for open-source collaboration and future changelog generation, while still keeping messages aligned with this repository's tone.
Format
<type>: <subject>
- Default style: formal Conventional Commits (
feat:,fix:,docs:,test:,chore:, etc.) - No scope parentheses by default — this repo usually does not use
type(scope):style; add a scope only if the user explicitly asks - Subject: imperative mood, lowercase first word, no trailing period, max ~72 chars
- Body (optional): blank line after subject, wrap at 72 chars, explain why not what
Types
| Type | When to use | Example |
|---|---|---|
feat |
New user-visible feature or capability | feat: add packed SFT dataset assembly workflow |
fix |
Bug fix | fix: prevent cross-sample attention leakage in packed runs |
docs |
Documentation, README, guides, skills, comments-only docs | docs: explain cu_lengths attention boundaries |
test |
Tests, fixtures, consistency checks, validation scripts | test: add HF/Megatron consistency checks for PP=2 |
refactor |
Code restructuring, no behavior change | refactor: move patch position block layout into task encoder |
chore |
Maintenance, internal cleanup, generated metadata, repo hygiene | chore: remove internal-only skill references |
perf |
Performance improvement without behavior change | perf: reduce token length scan overhead |
build |
Build system, dependencies, Docker, packaging | build: update flash attention to v2.7.0 |
ci |
CI/CD configuration and automation | ci: add packed dataset smoke test job |
style |
Formatting-only changes, no code behavior change | style: format offline packing scripts |
Notes:
featandfixare strongly preferred for code changes- Use
docsfor skill files under.opencode/skills/ - Avoid legacy bare messages like
updated,missing _extra_state, oradd OV2 SPunless the user explicitly asks to preserve old repo style RevertandMergeare generated by git — don't manually write these types
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.
- 2d ago First seen · 209 lines · 17 tokens per session scan A 4704874cb02a
commit-message is a skill published in the GitHub repository EvolvingLMMs-Lab/LLaVA-OneVision-2 (1,194 stars, last pushed 3d ago), licensed Apache-2.0. It adds 17 tokens to every session and 1,879 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-30.
Other skills, from other repositories
contributing
Use this skill when the user wants to contribute to MLX-VLM — opening a PR, where model code/config/tests go, backward-compatible config args, running the test suite, code formatting and the pre-commit hooks (black, clang-format), and PR expectations (tests, review, perf evidence). Use it to set up a change so it…
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
keploy-pr-workflow
Guide for creating PRs and issues on keploy repositories — PR format, customer-data hygiene, commit conventions, sign-off. Invoke when the user asks to open, update, or review a pull request or issue, when preparing a commit that will land in main, or whenever a change is about to leave the local machine.
add-new-model
Use this skill when the user wants to add or port a new model architecture to MLX-VLM — mapping a Hugging Face modeltype to a new file under mlxvlm/models, writing the ModelConfig, matching layer/weight names, reusing a similar existing model, adding a test class, and validating the port. Covers vision-language…