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/kwanpham2195/symphony-go/pushnpx skills add kwanpham2195/symphony-go --skill pushgit clone --depth 1 https://github.com/kwanpham2195/symphony-goWrote 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/kwanpham2195/symphony-go/push)<a href="https://agentmods.dev/skills/kwanpham2195/symphony-go/push"><img src="https://agentmods.dev/badge/skills/kwanpham2195/symphony-go/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.00029 | $0.00420 |
| Opus 5 | $0.00015 | $0.00210 |
| Sonnet 5 | $0.00006 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
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 5d 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.
What it actually says
Push
Prerequisites
ghCLI authenticated (gh auth status).
Steps
- Identify current branch:
branch=$(git branch --show-current) - Run validation before pushing:
make check - Push to origin:
git push -u origin HEAD - If push is rejected (non-fast-forward), use the
pullskill to sync, then retry. - If push fails due to auth/permissions, stop and surface the error.
- Ensure a PR exists:
pr_state=$(gh pr view --json state -q .state 2>/dev/null || true) if [ "$pr_state" = "MERGED" ] || [ "$pr_state" = "CLOSED" ]; then echo "Branch tied to closed PR; create a new branch + PR." exit 1 fi if [ -z "$pr_state" ]; then gh pr create --title "<clear title>" else gh pr edit --title "<updated title if scope changed>" fi - Write/update PR body with a clear description of the change.
- Reply with the PR URL:
gh pr view --json url -q .url - Move the Linear issue to In Review using the
linearskill so the orchestrator stops re-dispatching.
Notes
- Do not use
--force; only--force-with-leasewhen history was rewritten. - On branch updates, reconsider whether the PR title still matches the current scope.
- If the remote moved, use the
pullskill first — do not change remotes or protocols as a workaround.
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.
- 5d ago First seen · 57 lines · 29 tokens per session scan A bbb4542b31a2
push is a skill published in the GitHub repository kwanpham2195/symphony-go (10 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 420 once invoked, about $0.0001 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-31.
Other skills, from other repositories
codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
linear-cli
Manage Linear issues from the command line using the linear cli. This skill allows automating linear management.
Release
This skill should be used when the user asks to "make a release", "create a release", "cut a release", "release a new version", "publish a release", or mentions preparing for release. Provides comprehensive workflow for reviewing changes, updating changelog, determining semver bump, and publishing.
release-core-test
Invoke when dev-testing a Cyrus change that spans CYPACK (edgeworker + CLI) and CYHOST (Vercel-hosted GUI) and the hosted GUI needs to point at an unreleased cyrus-core from this repo. Publishes cyrus-core (and claude-runner if needed) as a -test.N prerelease under the npm test dist-tag so CYHOST can install it via…
cyrus-setup-claude-auth
Configure Claude Code authentication for Cyrus — API key, OAuth token, or third-party provider.
f1-test-drive
Orchestrate F1 test drives to validate the Cyrus agent system end-to-end across issue-tracker, EdgeWorker, and activity rendering.