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/kwanpham2195/symphony-go/commitnpx skills add kwanpham2195/symphony-go --skill commitgit clone --depth 1 https://github.com/kwanpham2195/symphony-goWhat 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.00036 | $0.00365 |
| Opus 5 | $0.00018 | $0.00182 |
| Sonnet 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 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.
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.
- 2d 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 3mo ago), licensed MIT. It adds 36 tokens to every session and 365 once invoked, about $0.0002 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-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.
codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
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.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…