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 rsts-dev/claude-buddy-marketplace --skill commitgit clone --depth 1 https://github.com/rsts-dev/claude-buddy-marketplaceWrote 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/rsts-dev/claude-buddy-marketplace/commit)<a href="https://agentmods.dev/skills/rsts-dev/claude-buddy-marketplace/commit"><img src="https://agentmods.dev/badge/skills/rsts-dev/claude-buddy-marketplace/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/rsts-dev/claude-buddy-marketplace/commit"><img src="https://agentmods.dev/badge/skills/rsts-dev/claude-buddy-marketplace/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00072 | $0.00439 |
| Opus 5.5 | $0.00029 | $0.00176 |
| Sonnet 5.5 | $0.00014 | $0.00088 |
| Haiku 4.5 | $0.00007 | $0.00044 |
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.
What it actually says
Commit
Ship the change through GitHub: a clean conventional commit, a push, and a PR that references the Jira ticket so the work traces end to end. Keep the human gate — commit after validation and review, not before.
Customization
Before executing, check ~/.claude/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Commit/PREFERENCES.md. If present, load and apply it; otherwise use defaults.
Prerequisites
- buddy + LifeOS installed (
test -f ~/.claude/LIFEOS/VERSION). gitand theghCLI (or the GitHub MCP). Without either, Commit makes the local commit and prints the PR command for the user to run.- Recommended:
/sdlc:validategreen and/sdlc:reviewaddressed first.
Workflow Routing
| Workflow | Trigger | File |
|---|---|---|
| CommitAndPR | Any /sdlc:commit invocation |
Workflows/CommitAndPR.md |
Delegation
For commit-message crafting and clean-commit rules, reuse buddy's SourceControl skill (its Commit workflow) when the buddy plugin is present; sdlc adds the push + GitHub PR + Jira linkage.
Output
A git commit, a pushed branch, and a GitHub PR linking the ticket.
Examples
User: "/sdlc:commit ABC-123"
→ Stages + writes a conventional commit (feat/fix/…): "feat: … (ABC-123)"
→ Pushes the branch
→ Opens a PR via gh; body links ABC-123 and summarizes the change
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 42 lines · 72 tokens per session scan A 7953a243e08b
Commit is a skill published in the GitHub repository rsts-dev/claude-buddy-marketplace (17 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 439 once invoked, about $0.0003 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-30.
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.
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…
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.