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 pushgit 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/push)<a href="https://agentmods.dev/skills/anantjain-xyz/symphony-rust/push"><img src="https://agentmods.dev/badge/skills/anantjain-xyz/symphony-rust/push.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.1 | $0.00046 | $0.00722 |
| Opus 5 | $0.00023 | $0.00361 |
| Sonnet 5 | $0.00009 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
symphony-push 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 7d 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
88% identical to symphony-push — 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Push
Preconditions
gh auth statussucceeds, and plaingit pushhas credentials for the repo host. If relying on GitHub CLI for HTTPS git credentials, rungh auth setup-gitfirst (gh auth setup-git --hostname <host>for a non-default host).GITHUB_TOKEN/GH_TOKENalone can authenticategh pr ...commands but is not enough forgit push -u origin HEAD.- Working tree is committed (use the
symphony-commitskill first). - The target repository's documented validation gate has been run for the latest commit.
Steps
- Identify the branch:
branch=$(git branch --show-current). - Push with upstream tracking:
git push -u origin HEAD - If the push is rejected as non-fast-forward, run the
symphony-pullskill to mergeorigin/main, re-run validation, then push again. Use--force-with-leaseonly when you knowingly rewrote history; never use--force. - Ensure a PR exists for the branch:
pr_state=$(gh pr view --json state -q .state 2>/dev/null || true)- Empty →
gh pr create --title "<title>" --body "<body>". OPEN→gh pr edit --title "<title>" --body "<body>"if scope shifted.CLOSED/MERGED→ branch is non-reusable; cut a fresh branch fromorigin/main.
- Empty →
- Title: short (< 70 chars), describes the outcome of the change, not the most recent fix. For Symphony issues, prefer
SYM-NN: <summary>. - Body: refresh to reflect total branch scope (not only the latest commits). Use the project's PR template if one exists.
- Apply the
symphonylabel via REST (thegh pr edit --add-labelpath 500s on this org due to a Projects-classic GraphQL deprecation):pr_number=$(gh pr view --json number -q .number) repo=$(gh repo view --json nameWithOwner -q .nameWithOwner) gh api -X POST "repos/${repo}/issues/${pr_number}/labels" -f 'labels[]=symphony' - Capture the PR URL:
gh pr view --json url -q .url. - Attach the PR URL to the active Linear issue. The auto-link from
git pushusually creates a Linear attachment automatically; if not, fall back to GraphQLattachmentLinkURL(orattachmentLinkGitHubPRfor GitHub-specific link metadata).
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.
- 7d ago First seen · 49 lines · 46 tokens per session scan A cc7a7e76a8ff
symphony-push is a skill published in the GitHub repository anantjain-xyz/symphony-rust (11 stars, last pushed 25d ago), licensed MIT. It adds 46 tokens to every session and 722 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to symphony-push, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
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.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".