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 anantjain-xyz/symphony-rust --skill 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/commit)<a href="https://agentmods.dev/skills/anantjain-xyz/symphony-rust/commit"><img src="https://agentmods.dev/badge/skills/anantjain-xyz/symphony-rust/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/anantjain-xyz/symphony-rust/commit"><img src="https://agentmods.dev/badge/skills/anantjain-xyz/symphony-rust/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.00040 | $0.00656 |
| Opus 5.5 | $0.00016 | $0.00262 |
| Sonnet 5.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 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.
This is a copy
100% identical to symphony-commit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 2mo 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 (12 stars, last pushed 16d ago), licensed MIT. It adds 40 tokens to every session and 656 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to symphony-commit, differing in 0 lines, and is treated as a copy.
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.
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.
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…