Borrowing it
Nothing to install: this file belongs to kwanpham2195/symphony-go. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kwanpham2195/symphony-go/main/.agents/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/kwanpham2195/symphony-goWrote 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/kwanpham2195/symphony-go/commit)<a href="https://agentmods.dev/skills/kwanpham2195/symphony-go/commit"><img src="https://agentmods.dev/badge/skills/kwanpham2195/symphony-go/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/kwanpham2195/symphony-go/commit"><img src="https://agentmods.dev/badge/skills/kwanpham2195/symphony-go/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.00036 | $0.00365 |
| Opus 5.5 | $0.00014 | $0.00146 |
| Sonnet 5.5 | $0.00007 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00036 |
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
Goals
- Produce a commit that reflects the actual code changes and the session context.
- Follow conventional commits (type prefix, short subject, wrapped body).
- Include both summary and rationale in the body.
Steps
- Read session history to identify scope, intent, and rationale.
- Inspect changes (
git status,git diff,git diff --staged). - Stage intended changes (
git add -A) after confirming scope. - Sanity-check newly added files; flag build artifacts, logs, or temp files before committing.
- Choose a conventional type and optional scope (e.g.,
feat(orchestrator):,fix(codex):,refactor(config):). - Write subject line in imperative mood, <= 72 characters, no trailing period.
- Write a body with:
- Summary of key changes (what changed).
- Rationale and trade-offs (why it changed).
- Tests or validation run (or note if not run).
- Wrap body lines at 72 characters.
- Create commit with
git commit -F <tempfile>(avoid-mwith\n). - Verify staged diff matches the commit message before committing.
Validation
Run before committing:
make check
Template
<type>(<scope>): <short summary>
Summary:
- <what changed>
Rationale:
- <why>
Tests:
- <command or "not run (reason)">
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 · 55 lines · 36 tokens per session scan A b2fe066e34b9
commit is a skill published in the GitHub repository kwanpham2195/symphony-go (10 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 365 once invoked, about $0.0001 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
commit
Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.
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…