Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/trueloving/pixuli/ref-issue-prnpx skills add trueLoving/Pixuli --skill ref-issue-prgit clone --depth 1 https://github.com/trueLoving/PixuliWrote 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/trueloving/pixuli/ref-issue-pr)<a href="https://agentmods.dev/skills/trueloving/pixuli/ref-issue-pr"><img src="https://agentmods.dev/badge/skills/trueloving/pixuli/ref-issue-pr.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.00503 |
| Opus 5 | $0.00023 | $0.00251 |
| Sonnet 5 | $0.00009 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
ref-issue-pr 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 4d 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
REF Issue → PR
Before coding
- Read issue body on GitHub (
gh issue view <n>) for 计划编号 (REF-xxx) - Open matching row in PLANS.md — check Depends on, Labels, 建议顺序
- Read linked docs under
docs/(not.local/unless available)
Implementation
- Smallest correct diff; match monorepo conventions (AGENTS.md)
- Run
pnpm test; add tests for provider/core changes - Do not commit unless user asks
PR
## Summary
- …
## Test plan
- [ ] pnpm test
- [ ] pnpm run ci
- [ ] …
Fixes #<issue> # only if PR fully closes the issue Related: REF-<id>
- Title:
[M4] REF-414 …orfix(m3): … (REF-313) - Link milestone label if applicable (
m4,refactor, etc.)
After merge
- Align with GitHub: issue should be
CLOSEDifFixes #nmerged - Update PLANS.md：对应行 状态 → ✅，或从「进行中」表移除
- 更新 Plans 文首 最近同步 日期；必要时跑
gh issue list --state open核对 OPEN 条数 - User-facing docs →
docs/01-product；Agent/Skill →AGENTS.md/.cursor/（仅架构边界变更时）
Add a new task
gh issue create（标题含[M4|M5|M6]，label / milestone 齐全）- 把
#number、标题、REF-id 写入 PLANS.md 对应里程碑表 - 需要排期时写入「当前焦点」表
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.
- 4d ago First seen · 58 lines · 47 tokens per session scan A 8604e12096ff
ref-issue-pr is a skill published in the GitHub repository trueLoving/Pixuli (67 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 503 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…