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 stone-w4tch3r/Figma-Context-MCP --skill sync-pr-branchgit clone --depth 1 https://github.com/stone-w4tch3r/Figma-Context-MCPWrote 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/stone-w4tch3r/figma-context-mcp/sync-pr-branch)<a href="https://agentmods.dev/skills/stone-w4tch3r/figma-context-mcp/sync-pr-branch"><img src="https://agentmods.dev/badge/skills/stone-w4tch3r/figma-context-mcp/sync-pr-branch/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/stone-w4tch3r/figma-context-mcp/sync-pr-branch"><img src="https://agentmods.dev/badge/skills/stone-w4tch3r/figma-context-mcp/sync-pr-branch.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.00019 | $0.00332 |
| Opus 5.5 | $0.00008 | $0.00133 |
| Sonnet 5.5 | $0.00004 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
sync-pr-branch 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.
What it actually says
Sync a PR branch with upstream to make it mergeable again.
Prerequisites: Upstream must already be fetched. Run /sync-fork first if the fork's main branch is also behind.
Steps
- Identify the PR:
gh pr list --state open --repo <upstream> --author <user>or checkgh pr view <number>. - Checkout the branch:
git checkout <branch>(fetch from origin if needed). - Merge upstream:
git merge upstream/main. - Resolve conflicts: Version files (package.json, lockfiles) — take upstream and regenerate. Code conflicts — keep both sides where additive, prefer upstream for structural changes.
- Fix post-merge issues: Run
pnpm install,pnpm type-check,pnpm build,pnpm test. Fix any breakage (e.g. jest→vitest migration, import changes). - Commit and push:
git add -A && git committhengit push origin <branch>. - Verify:
gh pr view <number> --repo <upstream> --json mergeable,mergeStateStatusshould show MERGEABLE/CLEAN. - Return to main:
git checkout main.
STOP and report for complex merge conflicts requiring complex logic understanding and rewriting or breaking API 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.
- 2mo ago First seen · 24 lines · 19 tokens per session scan A 01112731ab76
sync-pr-branch is a skill published in the GitHub repository stone-w4tch3r/Figma-Context-MCP (28 stars, last pushed 9d ago), licensed MIT. It adds 19 tokens to every session and 332 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It comes from a forked repository.
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.