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/anantjain-xyz/symphony-rust/pullnpx 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.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.00057 | $0.00746 |
| Opus 5 | $0.00028 | $0.00373 |
| Sonnet 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 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.
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.
- 5d 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 (11 stars, last pushed 23d ago), licensed MIT. It adds 57 tokens to every session and 746 once invoked, about $0.0003 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…