Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/m3taz-ahmed/ai-globalsnpx agentmods add skills/m3taz-ahmed/ai-globals/gsap-refactorWrote 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/m3taz-ahmed/ai-globals/gsap-refactor)<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/gsap-refactor"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/gsap-refactor/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/m3taz-ahmed/ai-globals/gsap-refactor"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/gsap-refactor.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.00076 | $0.00472 |
| Opus 5.5 | $0.00030 | $0.00189 |
| Sonnet 5.5 | $0.00015 | $0.00094 |
| Haiku 4.5 | $0.00008 | $0.00047 |
Grade A, and why
gsap-refactor 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 1mo 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
GSAP Refactor
Use this workflow for existing pages/components that already have code and may already have motion.
Sequence
- Read
.gsapartifacts first. - Read the actual implementation files.
- Run internal discovery, audit, and scan helpers.
- Detect framework, packages, routes, current motion libraries, and matched page files.
- Identify what to preserve, remove, simplify, or improve.
- Update
.gsap/audit-report.md,.gsap/animation-plan.md,.gsap/tasks/<page>.tasks.md, and.gsap/phases/<page>/*.md. - Split the refactor into phased sections instead of sweeping the full page at once.
- Apply safe changes to the active phase only unless the user asks for a broader pass.
- Update page artifact statuses and notes.
Internal Helper
Use:
python scripts/gsap_workflow.py gsap-refactor --path "<project>" --page "<page>"
This command should gather current workflow state, inspect the project structure, detect current motion systems, write audit/refactor notes, and prepare implementation state. It is the only public helper command for this mode.
Refactor Rules
- preserve good motion when possible
- remove noisy or redundant effects
- add reduced-motion handling where missing
- reduce mobile-heavy patterns before adding more spectacle
- do not change the motion direction without updating
.gsapartifacts
Completion
Before finishing, ensure:
.gsap/audit-report.mdrecords major findings and fixes.gsap/animation-plan.mdreflects the refactor priorities.gsap/tasks/<page>.tasks.mdreflects the current queue and active phase.gsap/phases/<page>/reflects the refactor section breakdown.gsap/pages/<page>.animation.mdreflects the final status
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 49 lines · 76 tokens per session scan A ce9192c299c3
gsap-refactor is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed 5d ago), licensed MIT. It adds 76 tokens to every session and 472 once invoked, about $0.0003 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…