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/browser-pr-review-workflow/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/browser-pr-review-workflow)<a href="https://agentmods.dev/skills/team-dongchimi/dongchimi-client/browser-pr-review-workflow"><img src="https://agentmods.dev/badge/skills/team-dongchimi/dongchimi-client/browser-pr-review-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/team-dongchimi/dongchimi-client/browser-pr-review-workflow"><img src="https://agentmods.dev/badge/skills/team-dongchimi/dongchimi-client/browser-pr-review-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.00036 | $0.01026 |
| Opus 5 | $0.00018 | $0.00513 |
| Sonnet 5 | $0.00007 | $0.00205 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
browser-pr-review-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 10d 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 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.
- 10d ago First seen · 97 lines · 36 tokens per session scan A c2da58bd51b3
browser-pr-review-workflow is a skill published in the GitHub repository TEAM-DONGCHIMI/DONGCHIMI-CLIENT (11 stars, last pushed 1mo ago), with no licence file. It adds 36 tokens to every session and 1,026 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
resolve-pr-feedback
Resolve GitHub PR review feedback with source-backed triage, fixes, autogoal plan state, focused proof, replies, and thread resolution.
understand-pr
Guided interactive PR review — understand the history and context before forming opinions.
tuturuuu-review-comments
Inspect, fix, and resolve Tuturuuu pull-request review threads.
create-pr
Create a branch, commit the work, and open a pull request for a completed user story, after all quality gates pass. Use when the user asks to open/create a PR or as the final step of the story workflow.
coverage-check
Run the repo's unit tests with coverage and verify that every file touched in the current change keeps line, branch, and function coverage at or above 95%. Language- and framework-agnostic. Use before committing, before PR creation, or when the user asks about coverage.
work-story
Work a user story end to end — fetch the ticket, plan (with approval), implement, verify the applicable gates, self-review, open the PR, and update the tracker. Use when given an issue key like PROJ-1234, ENG-42, or.