Borrowing it
Nothing to install: this file belongs to 363045841/KLineChartQuant. 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/363045841/KLineChartQuant/main/.opencode/skills/kline-blur-regression/SKILL.mdgit clone --depth 1 https://github.com/363045841/KLineChartQuantWrote 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/363045841/klinechartquant/kline-blur-regression)<a href="https://agentmods.dev/skills/363045841/klinechartquant/kline-blur-regression"><img src="https://agentmods.dev/badge/skills/363045841/klinechartquant/kline-blur-regression/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/363045841/klinechartquant/kline-blur-regression"><img src="https://agentmods.dev/badge/skills/363045841/klinechartquant/kline-blur-regression.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00857 |
| Opus 5 | $0.00023 | $0.00428 |
| Sonnet 5 | $0.00009 | $0.00171 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
kline-blur-regression 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.
What it actually says
K-line Blur Regression Skill
Goal
快速定位并修复这类回归:
- 正常时清晰,打开控制台/调整窗口后变糊;
- 多见于非整数 DPR(如 1.25, 1.5, 1.75);
- 用户要求“只在指定提交范围内找问题”。
When to use
触发关键词:
- “打开控制台后 K 线模糊/发糊”
- “DevTools 打开后变虚”
- “非整数 DPR 模糊”
- “只在某几个提交中排查”
Core principles
- 先定界再分析:严格按用户给的 commit 范围排查,不扩面。
- 优先查像素映射链路:Canvas backing store 尺寸、CSS 尺寸、
ctx.scale(dpr,dpr)是否一致。 - 最小修复:只改引入回归的 hunk,避免连带“优化”。
Investigation checklist
1) Build bounded diff
- 列出 commit 区间变更文件:
git diff --name-only <good_commit>..<bad_commit>
- 先看渲染核心路径:
src/core/paneRenderer.tssrc/core/chart.tssrc/core/renderers/yAxis.tssrc/utils/kLineDraw/axis.tssrc/core/renderers/Indicator/scale/*.ts
2) Prioritize high-risk patterns
重点检索以下改动:
canvas.width/height与style.width/height计算方式变化;Math.round(...)替换roundToPhysicalPixel(...);setTransform/scale调用顺序变化;- 轴宽来源从配置改为
canvas.width / dpr(或反之)。
3) Validate with minimal A/B
- 在 bad commit 复现;
- 只回滚单个可疑 hunk 再验证;
- 若恢复清晰,确认根因成立。
Known fix pattern (this repo)
本仓库一次已验证根因:PaneRenderer.resize() 中 CSS 尺寸策略改变导致非整数 DPR 下重采样风险上升。
修复方式(最小回退)是恢复:
plotCanvas.style.width = `${plotCanvas.width / dpr}px`
plotCanvas.style.height = `${plotCanvas.height / dpr}px`
yAxisCanvas.style.width = `${yAxisCanvas.width / dpr}px`
yAxisCanvas.style.height = `${yAxisCanvas.height / dpr}px`
而不是固定写逻辑尺寸:
plotCanvas.style.width = `${width}px`
plotCanvas.style.height = `${height}px`
Guardrails
- 不要把“用户限定范围外”的问题混入本次结论。
- 不要顺手改 unrelated 文件。
- 不要在未复现时给出肯定根因。
Verification steps
- 在非整数 DPR 环境(或系统缩放 125%/150%)运行。
- 记录打开 DevTools 前后 K 线清晰度是否变化。
- 触发一次 resize(拖动窗口/切换布局)。
- 确认修复后仍清晰,且无新错位(右轴/十字线/网格)。
Response template
- 先给“结论 + 文件行位点”;
- 再给“为什么只改这处”;
- 最后给“如何验证复现已消失”。
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 · 94 lines · 47 tokens per session scan A 4f155d2882ba
kline-blur-regression is a skill published in the GitHub repository 363045841/KLineChartQuant (24 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 857 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
update-skills
Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says "learn!", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
commit
Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style. Use when the user asks to 'commit', 'commit changes', 'create a commit', 'save my work', or 'check in code'.
sync
Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.
merge
Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…