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/anantjain-xyz/symphony-rust/symphony-commitnpx skills add anantjain-xyz/symphony-rust --skill symphony-commitgit clone --depth 1 https://github.com/anantjain-xyz/symphony-rustWrote 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/anantjain-xyz/symphony-rust/symphony-commit)<a href="https://agentmods.dev/skills/anantjain-xyz/symphony-rust/symphony-commit"><img src="https://agentmods.dev/badge/skills/anantjain-xyz/symphony-rust/symphony-commit.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.00656 |
| Opus 5 | $0.00020 | $0.00328 |
| Sonnet 5 | $0.00008 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
symphony-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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- symphony-commit — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
Goals
- Produce a commit whose subject and body match the actual staged diff and the session's intent.
- Follow the repo's existing convention (run
git log --oneline -20first; conventional-commit prefixes are common but the leading-identifier style —SYM-31:etc. — also appears). - Never
--no-verify. If a hook fails, fix the underlying problem and create a new commit.
Inputs
git status,git diff,git diff --stagedfor actual changes.- Recent commit messages on the branch and in
origin/mainfor style. - The Symphony Workpad on the current Linear issue for scope/intent.
Steps
- Inspect:
git status,git diff,git diff --staged. - Stage intended changes by name (
git add <paths>). Avoidgit add -A/git add .— they sweep in.env, credentials, large binaries, or artifacts you didn't mean to ship. - Sanity-check newly staged files. Build artifacts, logs, screenshots,
.symphony-workspace-ready, and locally injected fallback skills under.agents/skills/symphony-*or.claude/skillsmust stay unstaged unless the issue explicitly asks to install or change Symphony skills. Exception:.symphony/screenshots/<name>.pngis intentionally staged only by thesymphony-screenshotskill's temporary evidence commit (which also--no-verifys, the only place that's allowed); that skill then creates a cleanup revert commit so the files do not remain in the latest tree while the evidence commit remains in branch history. - Pick a subject (≤ 72 chars, imperative mood, no trailing period). Match the dominant style on the branch — usually
<TYPE>(<scope>): <summary>or<IDENTIFIER>: <summary>. - Write the body via heredoc so newlines are literal:
- One short paragraph (the why, plus tradeoffs if non-obvious).
- Optional bullets summarizing what changed across multiple files.
- Verify the message describes only what's staged. If the message and the diff disagree, fix the index — not the message.
- Run
git commit -F <file>(or the heredoc form) so newlines are real, not literal\n.
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.
- 4d ago First seen · 48 lines · 40 tokens per session scan A f8a8a8ccb5c6
symphony-commit is a skill published in the GitHub repository anantjain-xyz/symphony-rust (11 stars, last pushed 22d ago), licensed MIT. It adds 40 tokens to every session and 656 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-30.
Other skills, from other repositories
git-commit
Generate well-formatted git commit messages following conventional commit standards.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
commit
Commit current changes with a clear, descriptive message.
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…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…