Borrowing it
Nothing to install: this file belongs to kequach/uniqlo-sales-alerter. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kequach/uniqlo-sales-alerter/main/.agents/skills/uniqlo-change-workflow/SKILL.mdgit clone --depth 1 https://github.com/kequach/uniqlo-sales-alerterWrote 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/kequach/uniqlo-sales-alerter/uniqlo-change-workflow)<a href="https://agentmods.dev/skills/kequach/uniqlo-sales-alerter/uniqlo-change-workflow"><img src="https://agentmods.dev/badge/skills/kequach/uniqlo-sales-alerter/uniqlo-change-workflow/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/kequach/uniqlo-sales-alerter/uniqlo-change-workflow"><img src="https://agentmods.dev/badge/skills/kequach/uniqlo-sales-alerter/uniqlo-change-workflow.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.00064 | $0.00823 |
| Opus 5 | $0.00032 | $0.00411 |
| Sonnet 5 | $0.00013 | $0.00165 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
uniqlo-change-workflow 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 11d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Uniqlo Change Workflow
Use this skill to keep material Uniqlo Sales Alerter changes scoped, verified, and reviewable without adding ceremony to small edits.
1. Load The Local Contract
Before editing, read the relevant parts of:
AGENTS.mddocs/CODEX_WORKFLOW.mdpyproject.toml- The files directly involved in the requested change
- Existing
.cursor/rules/only when you need extra detail behind AGENTS.md
If the request touches Uniqlo API retrieval, stock verification, filtering, country capabilities, product URLs, notifications, config persistence, secrets, Docker, or release behavior, treat it as integration-sensitive.
2. Scope Before Editing
For material changes, write a short plan in the thread:
- Goal
- Non-goals
- Files likely to change
- Acceptance checks
- Test/verification commands
- README/config/changelog impact
Ask one concise clarifying question only when a wrong assumption would create user-visible behavior, broken notifications, lost config/state, leaked secrets, or release risk.
3. Implement Narrowly
Follow existing Python, FastAPI, Pydantic, httpx, notification, config, and test patterns. Keep changes close to the requested behavior. Do not add browser automation, scraping outside the existing API approach, new notification providers, new persistence formats, new network services, or new dependencies without explicit user approval.
4. Route Specialist Review Intentionally
Use a repo-local, router-first topology:
- The main Codex agent owns implementation and decides whether focused review is needed.
- For most material diffs, route once to
uniqlo-code-reviewer. - Add
uniqlo-integration-revieweronly for API, stock, filtering, CountryCapabilities, URL, notification, config, secret, Docker, or release risk. - Treat each subagent TOML as the agent card: it defines the agent's role, capabilities, required context, and expected findings format.
- Keep subagents as direct children. Do not introduce MCP, A2A, registries, or extra orchestration for normal repo work.
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.
- 11d ago First seen · 93 lines · 64 tokens per session scan A dcd333cd695f
uniqlo-change-workflow is a skill published in the GitHub repository kequach/uniqlo-sales-alerter (30 stars, last pushed 22d ago), licensed MIT. It adds 64 tokens to every session and 823 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-09-01.
Other skills, from other repositories
scaffold-dotnet-test-project
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero"…
cy-execute-task
Implement and verify an existing CompozyOS spec task, then update its tracking. Excludes review remediation.
team-qa
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.