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/reorder-js/reorder/sync-docsnpx skills add reorder-js/reorder --skill sync-docsgit clone --depth 1 https://github.com/reorder-js/reorderWhat 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 | $0.00039 | $0.00609 |
| Opus 5 | $0.00019 | $0.00304 |
| Sonnet 5 | $0.00008 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
sync-docs 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 3d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Documentation (Internal Docs & Public Mintlify)
This skill manages the two-stage documentation synchronization workflow:
- Internal Technical Docs (
reorder/docs/): Source of truth for developers and AI agents (architecture, APIs, testing, admin UX, scripts). - Public Mintlify Docs (
../docs/): Customer-facing documentation (MDX format) for merchants and developers using the plugin.
When to trigger
- Automatically: Whenever you successfully
git pushcode changes to thereorderrepository, ALWAYS ask the user: "Czy zmiany wymagają aktualizacji dokumentacji (wewnętrznej w reorder/docs lub publicznej Mintlify w ../docs)? Jeśli tak, użyję skilla sync-docs." - Manually: When the user asks to "sync docs", "update documentation", "zaktualizuj docs", or runs
/sync-docs.
2-Stage Synchronization Workflow
Stage 1: Verify & Update Internal Technical Docs (reorder/docs/)
Before updating public docs, ensure the internal source of truth is 100% accurate:
- Check changed code, workflows, API contracts, domain models, or scripts in
reorder. - Update the corresponding documents in
reorder/docs/:docs/architecture/for domain architecture or lifecycle changesdocs/api/for Admin or Store route changesdocs/admin/for UI flow, filter, or widget changesdocs/testing/for new test utilities, scripts, or coveragedocs/README.mdfor index and roadmap updates
- If changes were made to
reorder/docs/, commit them to thereorderrepository (propose Conventional Commit e.g.docs: update internal documentation for <feature>).
Stage 2: Sync to Public Mintlify Repository (../docs/)
Only after internal docs are accurate:
- Navigate to
../docsand ensure your local branch is synchronized with remote before making any edits (git pull). - Read
../docs/AGENTS.mdto review style guidelines, terminology, and content boundaries (do not expose internal locking/scheduler details). - Update or create corresponding
.mdxfiles in../docs. - Update
../docs/docs.jsonnavigation structure if new pages were introduced. - Review changes with
git statusandgit diff. - Propose a Conventional Commit message (e.g.
docs: update <feature> guide), wait for approval, and push to thedocsremote repository (git push). - Report completion to the user.
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.
- 3d ago First seen · 38 lines · 39 tokens per session scan A 4a9514ac5927
sync-docs is a skill published in the GitHub repository reorder-js/reorder (51 stars, last pushed 9d ago), licensed MIT. It adds 39 tokens to every session and 609 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.
Other skills, from other repositories
task-manager
Capture actionable user requests as persistent tasks, update task status as work progresses, and keep a shared task store in sync. Use when a user asks an agent to do work, check progress, block a task, complete a task, or manage the Kanban board.
soundclaw
Control Spotify playback, search music, and return shareable music links.
todo
Maintain a shared workspace TODO list with blocked tasks.
saleor-paper-storefront
Project-specific patterns for the Saleor Paper storefront built with Next.js 16, TypeScript, and Tailwind CSS. Use when working with product pages, checkout flow, caching, variant selection, filtering, SEO, or UI components. For universal Saleor API patterns, see the saleor-storefront dependency.
paper-migrations
Apply chronological Paper storefront upgrades to a forked shop. Use when the user says upgrade Paper, apply Paper migrations, catch up with upstream caching, or paper-version. Reads migrations/manifest.json and paper-version.json; ports architecture without overwriting custom styling.
storefront-best-practices
ALWAYS use this skill when working on ecommerce storefronts, online stores, shopping sites. Use for ANY storefront component including checkout pages, cart, payment flows, product pages, product listings, navigation, homepage, or ANY page/component in a storefront. CRITICAL for adding checkout, implementing cart…