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/hueanmy/qa-playwright-agent/sync-testsnpx skills add hueanmy/qa-playwright-agent --skill sync-testsgit clone --depth 1 https://github.com/hueanmy/qa-playwright-agentWrote 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/hueanmy/qa-playwright-agent/sync-tests)<a href="https://agentmods.dev/skills/hueanmy/qa-playwright-agent/sync-tests"><img src="https://agentmods.dev/badge/skills/hueanmy/qa-playwright-agent/sync-tests.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.00055 | $0.00820 |
| Opus 5 | $0.00028 | $0.00410 |
| Sonnet 5 | $0.00011 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
sync-tests 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Tests
Copy generated artifacts from ${user_config.output_dir}/${user_config.app_name}/ into ${user_config.target_repo} according to the user's sync.config.json.
Inputs
${user_config.app_name}— slug${user_config.output_dir}— source base (defaultoutput/)${user_config.target_repo}— destination repo path${user_config.playwright_test_dir}— relative subdir in the target repo (defaulte2e/tests)$ARGUMENTS— pass--dry-runto preview without copying
Steps
- Locate the sync config. Look for
${user_config.output_dir}/../apps/${user_config.app_name}/sync.config.json, then./sync.config.jsonat project root, then fall back to the default mapping below. - Verify the target repo exists. If
${user_config.target_repo}doesn't exist, stop and tell the user. - Run the sync. Prefer the bundled helper script:
If that script is unavailable, fall back tobash "${CLAUDE_PLUGIN_ROOT}/scripts/sync.sh" \ --source "${user_config.output_dir}/${user_config.app_name}" \ --target "${user_config.target_repo}" \ --tests-dir "${user_config.playwright_test_dir}" \ [--dry-run]cp -Rwith the mappings below, respecting the dry-run flag. - Report every file copied (or, in dry-run, every file that would be copied), grouped by mapping.
Default mapping
If no sync.config.json is found, use these defaults:
Source (under ${output_dir}/${app_name}/) |
Destination (under ${target_repo}/) |
Overwrite |
|---|---|---|
tests/ |
${user_config.playwright_test_dir} |
no |
healed/ |
${user_config.playwright_test_dir} |
yes |
plans/ |
e2e/plans/ |
no |
reports/ |
e2e/reports/ |
no |
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 · 68 lines · 55 tokens per session scan A 1025f0055939
sync-tests is a skill published in the GitHub repository hueanmy/qa-playwright-agent (2 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 820 once invoked, about $0.0003 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-31.
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…