agentmods.dev

symphony-rust: Skill for Claude Code

.agents/skills/symphony-push/SKILL.md

symphony-push is a skill for Claude Code, Codex from anantjain-xyz/symphony-rust. It costs 46 tokens per session (728 once invoked), scanned A, original, MIT.

A workflow for pushing the current Git branch to its remote repository and making sure a GitHub pull request exists for it. A pull request is a proposed code change that others can review before it is merged.

In plain words
What is it for?
It helps publish a branch, create or update its pull request, apply the symphony label, and handle rejected pushes caused by diverging history.
Why use it?
It collects the checks and steps needed after code is committed, including validation, pushing, and creating or updating the pull request. It also describes what to do when the remote branch has newer changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is anantjain-xyz/symphony-rust's own configuration. It tells Claude Code and Codex how to work on symphony-rust itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything symphony-rust configures →

not rated 11repo 27d ago A scan 46 tokens original MIT
View source ↗ anantjain-xyz/symphony-rust
Reuse

Borrowing it

Nothing to install: this file belongs to anantjain-xyz/symphony-rust. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/anantjain-xyz/symphony-rust/main/.agents/skills/symphony-push/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/anantjain-xyz/symphony-rust

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for symphony-push

README.md
[![agentmods](https://agentmods.dev/badge/skills/anantjain-xyz/symphony-rust/symphony-push/github.svg)](https://agentmods.dev/skills/anantjain-xyz/symphony-rust/symphony-push)
Your own site
<a href="https://agentmods.dev/skills/anantjain-xyz/symphony-rust/symphony-push"><img src="https://agentmods.dev/badge/skills/anantjain-xyz/symphony-rust/symphony-push/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.

agentmods 80×15 button for symphony-push

Your own site · 80×15
<a href="https://agentmods.dev/skills/anantjain-xyz/symphony-rust/symphony-push"><img src="https://agentmods.dev/badge/skills/anantjain-xyz/symphony-rust/symphony-push.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 728 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.00728
Opus 5 $0.00023 $0.00364
Sonnet 5 $0.00009 $0.00146
Haiku 4.5 $0.00005 $0.00073

Measured 9d ago against content hash f82d38aef3ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 9d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/skills/symphony-push/SKILL.md · 49 lines

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 status succeeds, and plain git push has credentials for the repo host. If relying on GitHub CLI for HTTPS git credentials, run gh auth setup-git first (gh auth setup-git --hostname <host> for a non-default host). GITHUB_TOKEN/GH_TOKEN alone can authenticate gh pr ... commands but is not enough for git push -u origin HEAD.
  • Working tree is committed (use the symphony-commit skill first).
  • The local pre-push gate has been run for the latest commit (pnpm verify:fast).

Steps

  1. Identify the branch: branch=$(git branch --show-current).
  2. Push with upstream tracking: 
    git push -u origin HEAD
  3. If the push is rejected as non-fast-forward, run the symphony-pull skill to merge origin/main, re-run validation, then push again. Use --force-with-lease only when you knowingly rewrote history; never use --force.
  4. 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 from origin/main.
  5. Title: short (< 70 chars), describes the outcome of the change, not the most recent fix. For Symphony issues, prefer SYM-NN: <summary>.
  6. Body: refresh to reflect total branch scope (not only the latest commits). Use the project's PR template if one exists.
  7. Apply the symphony label via REST (the gh pr edit --add-label path 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'
  8. Capture the PR URL: gh pr view --json url -q .url.
  9. Attach the PR URL to the active Linear issue. The auto-link from git push usually creates a Linear attachment automatically; if not, fall back to GraphQL attachmentLinkURL (or attachmentLinkGitHubPR for GitHub-specific link metadata).

Read the full file on GitHub · 49 lines

Changes

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.

  1. 9d ago First seen · 49 lines · 46 tokens per session scan A f82d38aef3ae

Subscribe to this mod's changes

symphony-push is a skill published in the GitHub repository anantjain-xyz/symphony-rust (11 stars, last pushed 27d ago), licensed MIT. It adds 46 tokens to every session and 728 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.

Code reviewGit and workflow
Related

Other skills, from other repositories

review-implement-phase

Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.

prisma/orm · 38 tokens

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

Gentleman-Programming/engram · 37 tokens

verify-behavior

Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…

nicknisi/dotfiles · 68 tokens

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…

daymade/claude-code-skills · 133 tokens

revdiff

Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…

umputun/revdiff · 248 tokens

write-pr

Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.

tldraw/tldraw · 53 tokens