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 rekabytes/opencode-skills --skill commitgit clone --depth 1 https://github.com/rekabytes/opencode-skillsWrote 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/rekabytes/opencode-skills/commit)<a href="https://agentmods.dev/skills/rekabytes/opencode-skills/commit"><img src="https://agentmods.dev/badge/skills/rekabytes/opencode-skills/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/rekabytes/opencode-skills/commit"><img src="https://agentmods.dev/badge/skills/rekabytes/opencode-skills/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.00008 | $0.00306 |
| Opus 5.5 | $0.00003 | $0.00122 |
| Sonnet 5.5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00031 |
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 2mo 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
Commit Message Conventions
Format
type(scope): description
- Bullet point changes
- Multiple lines if needed
Type Prefixes
feat- New featurefix- Bug fixrefactor- Code refactoringUI- UI changeschore- Maintenance/tasksdocs- Documentationtest- Testing
Scope Rules
- Always include scope in parentheses
- Valid scopes:
backend,frontend,mobile,webapp,db,infra, etc. - type prefixes changes MUST use e.g
UI(frontend):orfix(mobile):
Examples
feat(backend): add user authentication
- Implement JWT token validation
- Add protectedProcedure middleware
- Update user model with auth fields
UI(frontend): redesign lobby screen
- Update component styles
- Fix scroll issues on create room modal
fix(mobile): resolve navigation bug
- Fix back button behavior on iOS
- Update navigation stack logic
Rules
- Always use lowercase for type and scope
- Use imperative mood (add, fix, update - not added, fixed, updated)
- Keep first line under 72 characters
- Add detailed bullet points for complex changes
- Scope is REQUIRED - never commit without it
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.
- 2mo ago First seen · 55 lines · 8 tokens per session scan A 4afa1fb2ba14
commit is a skill published in the GitHub repository rekabytes/opencode-skills (5 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 306 once invoked, about $0.0000 per session on Opus 5.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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…