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 pullgit 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/pull)<a href="https://agentmods.dev/skills/anantjain-xyz/symphony-rust/pull"><img src="https://agentmods.dev/badge/skills/anantjain-xyz/symphony-rust/pull/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/pull"><img src="https://agentmods.dev/badge/skills/anantjain-xyz/symphony-rust/pull.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.00057 | $0.00746 |
| Opus 5.5 | $0.00023 | $0.00298 |
| Sonnet 5.5 | $0.00011 | $0.00149 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
symphony-pull 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
94% identical to symphony-pull — 2 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull
Goals
- Bring
origin/maininto the working branch with a real merge commit so reviewers can see the integration. - Resolve conflicts in code (not by deleting state). Never use
git reset --hard,git push --force*, orgit clean -f*to "make it go away". - After merging, the PR should report
MERGEABLEandCLEAN/HAS_HOOKS/UNSTABLE— neverCONFLICTING/DIRTY.
Steps
- Working tree must be clean. Either commit (
symphony-commitskill) orgit stashfirst. - Enable rerere once per workspace so repeated conflicts auto-resolve:
git config rerere.enabled true git config rerere.autoupdate true - Fetch refs:
git fetch origin. - If a remote feature branch is ahead (e.g. CI auto-formatted), fast-forward first:
git pull --ff-only origin "$(git branch --show-current)" || true - Merge
origin/mainwith a clearer conflict style:git -c merge.conflictstyle=zdiff3 merge origin/main - Resolve conflicts (see below), then
git add <files>andgit merge --continue(orgit commitif the merge auto-paused). - Re-run the target repository's documented validation gate before pushing.
- Record the result in the workpad's
### Notes(e.g.merge origin/main: cleanorconflicts resolved: <files>) and the new short SHA.
Resolving conflicts
git statuslists the conflicted files;git diffshows hunks.merge.conflictstyle=zdiff3produces<<<<<<< ours,||||||| base,>>>>>>> theirsmarkers with surrounding shared context trimmed — focus on the differing core.- For each file, decide the intent of both sides before editing:
- What is each side trying to do? (bugfix, refactor, rename, behavior change.)
- Is one side strictly newer / superseding? Or are they orthogonal and both must be kept?
- What invariant must hold after the merge?
- Prefer minimal, intent-preserving edits. Don't silently drop one side; if you intend to drop something, do it explicitly.
- For generated files, regenerate after resolving the source-of-truth files (don't hand-merge generated output).
- For import lists where intent is unclear, accept both sides, then let lint/typecheck strip what isn't used.
- After every file:
git diff --check— if it complains about conflict markers, you missed one. - Use
git checkout --ours <file>/--theirs <file>only when you are certain one side wins entirely.
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 · 52 lines · 57 tokens per session scan A 54fce3790d95
symphony-pull is a skill published in the GitHub repository anantjain-xyz/symphony-rust (12 stars, last pushed 16d ago), licensed MIT. It adds 57 tokens to every session and 746 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to symphony-pull, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.