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-forkgit 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-fork)<a href="https://agentmods.dev/skills/stone-w4tch3r/figma-context-mcp/sync-fork"><img src="https://agentmods.dev/badge/skills/stone-w4tch3r/figma-context-mcp/sync-fork.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.00022 | $0.01973 |
| Opus 5 | $0.00011 | $0.00986 |
| Sonnet 5 | $0.00004 | $0.00395 |
| Haiku 4.5 | $0.00002 | $0.00197 |
Grade A, and why
sync-fork 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync fork with upstream repository, handle all simple issues automatically, ensure version bump, and publish to NPM. Follow these steps, verifying after each step before proceeding.
IMPORTANT: After every upstream merge, a version bump and NPM release is ALWAYS performed - even if upstream had no version changes, we apply a custom minor version bump to the fork.
Prerequisites
- Must be in a git repository with upstream configured
- GitHub CLI (gh) must be installed and authenticated
- Upstream remote must be named "upstream"
Step-by-Step Process
1. Verify Repository State
- Check:
git remote -v- Verify upstream remote exists - Check:
git status- Ensure working tree is clean (no uncommitted changes) - If working tree is dirty, STOP and report to user
2. Fetch Upstream Changes
- Run:
git fetch upstream - Verify: Check if upstream/main has new commits compared to current HEAD
- Run:
git log origin/main..upstream/main --onelineto see commits behind - Run:
git log upstream/main..origin/main --onelineto see commits ahead
3. Merge Upstream into Main
- Run:
git merge upstream/main - Auto-fix if possible:
- Simple conflicts (whitespace, trivial merges) - resolve automatically
- Changeset conflicts - update package name references if known
- For complex conflicts or merge conflicts: STOP and report immediately
- Verify:
git statusshows successful merge
4. Handle Common Post-Merge Issues
Changeset package name mismatch:
- If error mentions changeset package name not in workspace:
- Check package.json for actual package name
- Update .changeset/*.md files to use correct package name
- Commit and push fix
- This is safe to auto-fix
Dependencies changes:
- If package.json has dependency conflicts or outdated versions:
- Run:
pnpm installto resolve - Update lockfile and commit
- Safe to auto-fix
- Run:
Minor renamings:
- If import paths or exports changed:
- Find all references and update to match new structure
- Test with
pnpm type-checkandpnpm build - Commit fixes
- Safe to auto-fix for obvious patterns
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.
- 8d ago First seen · 224 lines · 22 tokens per session scan A 5ec558867265
sync-fork is a skill published in the GitHub repository stone-w4tch3r/Figma-Context-MCP (29 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 1,973 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
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".
updater_guide
Guidance for checking for and installing Row-Bot updates.