Borrowing it
Nothing to install: this file belongs to haoxiang-xu/PuPu. 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/haoxiang-xu/PuPu/main/.agents/skills/community-repo-tags-optimization/SKILL.mdgit clone --depth 1 https://github.com/haoxiang-xu/PuPuWrote 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/haoxiang-xu/pupu/community-repo-tags-optimization)<a href="https://agentmods.dev/skills/haoxiang-xu/pupu/community-repo-tags-optimization"><img src="https://agentmods.dev/badge/skills/haoxiang-xu/pupu/community-repo-tags-optimization/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/haoxiang-xu/pupu/community-repo-tags-optimization"><img src="https://agentmods.dev/badge/skills/haoxiang-xu/pupu/community-repo-tags-optimization.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.00097 | $0.01620 |
| Opus 5.5 | $0.00039 | $0.00648 |
| Sonnet 5.5 | $0.00019 | $0.00324 |
| Haiku 4.5 | $0.00010 | $0.00162 |
Grade A, and why
community-repo-tags-optimization 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 28d 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community: Repository Tags Optimization
Optimize haoxiang-xu/PuPu's topics with product fit, measured visibility and preserved growth evidence. Use community-growth-analyst for traffic and installer accounting; reuse valid same-day snapshots.
Owner's current operating rule — clarified 2026-09-22
- Keep exactly 20 unique live topics, partitioned into A: 10 and B: 10. Both groups are on GitHub simultaneously. There is no permanent 15-topic core and no whole-set A/B alternation.
- Each group has a 14-day review/holding cycle, with the two groups' review dates seven days apart. Every week only one group is eligible for optimization; the other group stays unchanged.
- Optimize only part of the due group: normally 1–3 substitutions, at most 5. Keep well-supported topics and allow zero changes when retention or insufficient evidence warrants it. Never replace an entire group merely because its review is due.
- The owner has authorized this recurring, evidence-based partial optimization, including selecting fresh relevant candidates at the scheduled review. Do not request the same permission again. This authority covers GitHub topics and growth records, not README, description, releases, issues or unrelated settings.
- Small or rarely used meaningful tags are allowed when they match shipped PuPu capabilities and give plausible visibility. Do not leave slots empty.
Records
Use .claude/archive/growth/ in this checkout. Preserve historical snapshots and append-only event history.
| File | Purpose |
|---|---|
topics-weekly-rotation.json |
Current simultaneous 10+10 membership, per-group revision, exposure evidence and next review dates. Despite the historical filename, this is staggered partial optimization, not whole-set rotation. |
topics-history.ndjson |
Append one measurement or policy event per run, including unchanged runs. Include live topics, volumes, metric collection time, A/B revisions and any change/retention decision. |
YYYY-MM-DD-topics-change.md |
Before each actual GitHub mutation, record old/new complete sets, due group, changed subset, rationale and rollback command. |
| Dated snapshots/reports | Raw views, clones, referrers, paths, repository totals, stargazer dates and paginated release counters with collection time, UTC coverage and errors. |
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.
- 28d ago Changed · +9 lines 7e82541d8847
- 1mo ago First seen · 43 lines · 97 tokens per session scan A 46d1d08f80f7
community-repo-tags-optimization is a skill published in the GitHub repository haoxiang-xu/PuPu (36 stars, last pushed 3d ago), licensed Apache-2.0. It adds 97 tokens to every session and 1,620 once invoked, about $0.0004 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-09-21.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…