Borrowing it
Nothing to install: this file belongs to TEAM-DONGCHIMI/DONGCHIMI-CLIENT. 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/TEAM-DONGCHIMI/DONGCHIMI-CLIENT/develop/.agents/skills/frontend-predictability-check/SKILL.mdgit clone --depth 1 https://github.com/TEAM-DONGCHIMI/DONGCHIMI-CLIENTWrote 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/team-dongchimi/dongchimi-client/frontend-predictability-check)<a href="https://agentmods.dev/skills/team-dongchimi/dongchimi-client/frontend-predictability-check"><img src="https://agentmods.dev/badge/skills/team-dongchimi/dongchimi-client/frontend-predictability-check/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/team-dongchimi/dongchimi-client/frontend-predictability-check"><img src="https://agentmods.dev/badge/skills/team-dongchimi/dongchimi-client/frontend-predictability-check.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.00047 | $0.00684 |
| Opus 5 | $0.00023 | $0.00342 |
| Sonnet 5 | $0.00009 | $0.00137 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
frontend-predictability-check 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 9d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 9d ago First seen · 87 lines · 47 tokens per session scan A 23d49e13aa47
frontend-predictability-check is a skill published in the GitHub repository TEAM-DONGCHIMI/DONGCHIMI-CLIENT (11 stars, last pushed 1mo ago), with no licence file. It adds 47 tokens to every session and 684 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
spotpatch
A development workflow for React that connects a selected page element to its JSX or TSX source code and gathers context for review.
next-application-structure
Establishes or reviews directory layout, server/client boundaries, routing, data-fetching strategy, and testing structure for Next.js 14+ App Router TypeScript applications. Invoked when the user asks to structure a Next app, set App Router conventions, or review architecture for React parity.
Component Test Scaffold (Next.js)
Generate React/Next.js component test skeletons (RTL) from specifications.
fe-build
Implements frontend components and pages for React / Next.js / Vite SPA + TypeScript projects. Use when: starting implementation after feature.md or a spec is approved, writing components, building pages. Do NOT load for: writing specs, code review, bug analysis.
Next.js App Router Client/Server Boundary
A review rule for Next.js App Router components that checks whether server-side components use browser-only React hooks or browser APIs.
frontend-code-review
Review React, Next.js App Router, TypeScript, Tailwind CSS, shadcn/ui, TanStack Query, and frontend UI code. Use when reviewing a PR, branch, diff, page, component, hook, Server Action, route handler, or API client; debugging frontend behavior; assessing production readiness; or checking runtime bugs, client/server…