Borrowing it
Nothing to install: this file belongs to Dimkox/adaptive-grok-build-pro. 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/Dimkox/adaptive-grok-build-pro/main/.agents/skills/frontend-change/SKILL.mdgit clone --depth 1 https://github.com/Dimkox/adaptive-grok-build-proWrote 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/dimkox/adaptive-grok-build-pro/frontend-change)<a href="https://agentmods.dev/skills/dimkox/adaptive-grok-build-pro/frontend-change"><img src="https://agentmods.dev/badge/skills/dimkox/adaptive-grok-build-pro/frontend-change/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/dimkox/adaptive-grok-build-pro/frontend-change"><img src="https://agentmods.dev/badge/skills/dimkox/adaptive-grok-build-pro/frontend-change.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.00029 | $0.00105 |
| Opus 5.5 | $0.00012 | $0.00042 |
| Sonnet 5.5 | $0.00006 | $0.00021 |
| Haiku 4.5 | $0.00003 | $0.00011 |
Grade A, and why
frontend-change 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 2mo 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
Frontend Change
Cover normal, loading, empty, error, offline, permission, and responsive states. Preserve API compatibility, keyboard navigation, focus, labels, semantic structure, and performance. Use browser evidence for regressions. Add focused component and critical-path E2E tests; run lint, typecheck, tests, and build when configured.
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.
- 2mo ago First seen · 9 lines · 29 tokens per session scan A 0b841164bc11
frontend-change is a skill published in the GitHub repository Dimkox/adaptive-grok-build-pro (2 stars, last pushed 23d ago), licensed MIT. It adds 29 tokens to every session and 105 once invoked, about $0.0001 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
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…
next-partial-prefetching-optimizer
Optimize what selected Next.js client navigations include before the click under Partial Prefetching. Use after Cache Components and Partial Prefetching are adopted when the user wants selected URL-specific UI to be instant, wants reusable content to wait for navigation, or needs to choose between default, viewport…
verify
Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
uat-signoff
Walk a business/UAT approver through a plain-language demo of a verified feature and capture business acceptance signoff.