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/cooler333/cool-claude-code/maintain-ranking-scriptsnpx skills add cooler333/cool-claude-code --skill maintain-ranking-scriptsgit clone --depth 1 https://github.com/cooler333/cool-claude-codeWrote 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/cooler333/cool-claude-code/maintain-ranking-scripts)<a href="https://agentmods.dev/skills/cooler333/cool-claude-code/maintain-ranking-scripts"><img src="https://agentmods.dev/badge/skills/cooler333/cool-claude-code/maintain-ranking-scripts.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.00108 | $0.03676 |
| Opus 5 | $0.00054 | $0.01838 |
| Sonnet 5 | $0.00022 | $0.00735 |
| Haiku 4.5 | $0.00011 | $0.00368 |
Grade A, and why
maintain-ranking-scripts 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 3d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
maintain-ranking-scripts
Maintain the scripts behind this repo's auto-generated, star-ranked README of the Claude Code / skills / agents / MCP ecosystem.
What this repo's pipeline does
helpers/fetch.py(network only) does an exhaustive star-bucketed sweep of every public repo at or abovemin_stars(the Search API caps each query at 1,000 results, so the star range is split into adaptive buckets, then concatenated). Because the sweep is exhaustive, discovery is complete by construction — there are no scoped queries that could miss a popular repo. It writes two files and nothing else:helpers/repos.json— the full universe (every repo ≥min_stars), metadata only. The single source of truth for everything downstream.helpers/out_of_scope.json— AUTO classification: universe entries that failscope_filter(not AI/Claude). Regenerated every run; never hand-edited. It does not categorize, write briefs, rank-to-top-N, fetch READMEs, or apply any denylist.
helpers/render.py(no network) selects the published set —repos.jsonminusout_of_scope.jsonminushelpers/filtered.jsonminus archived, toprender.render_countby stars — writeshelpers/repos_to_render.json, then categorizes, builds the short briefs (from description / topics), and lays outREADME.md: a Table of Contents, the Trending this week cut, the Top-N leaderboard, the long tail split into per-category tables, and a footer of links. The README body is tables only — the prose (scope, column definitions, disclaimer, licensing) lives in hand-maintained docs, not inrender.py; see "Where the static docs live" below.helpers/trend.py(no network, git only) supplies the momentum columns (Pos,+Stars) and the Trending cut: it reads an older committed version ofrepos.jsonstraight out of git history — the newest snapshot at leastrender.trend.window_daysold. One baseline feeds both columns, so they always describe the same span. No extra API calls and no new state file; the daily commits are the star history. Best-effort: no git, a depth-1 clone, or history shorter than the window drops both columns and the Trending section, and the README still renders.- CI (
.github/workflows/):refresh-ranking.ymlruns the sweep+render daily and commits the artifacts;render-on-edit.ymlre-renders (no network) when a human editsfiltered.json(NOTconfig.json— scope/min_stars are sweep-time, so config edits wait for the next sweep). Both check out withfetch-depth: 0— the default depth-1 clone would silently render without the momentum columns.
What ships with it
2 files 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.
- 3d ago First seen · 222 lines · 108 tokens per session scan A 7c8364311c68
maintain-ranking-scripts is a skill published in the GitHub repository cooler333/cool-claude-code (9 stars, last pushed 4d ago), licensed CC0-1.0. It adds 108 tokens to every session and 3,676 once invoked, about $0.0005 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-31.
Other skills, from other repositories
unity-agent-workflows
Use for AI-assisted Unity work that needs live repo discovery, project-derived routing, runtime-owner proof, runtime-visible output hard stops, runtime numeric proof for repeated visible-output failures, state-step guards, multi-agent scope ownership, modular C#/asmdef safety, UI/scene/visual asset gates, data-first…
interpreting-mod-author-instructions
Use when deciding how to correctly download/install a Bethesda mod per the author's instructions — triggers "how do I install", "FOMOD choices", "which file to download", "author说明", "install instructions", "which variant", "按作者说明安装", "这个mod怎么装". NOT for deciding whether to include the mod (use evaluating-bgs-mods)…
diagnosing-bgs-problems
Use when a BGS modded game has CTD, crash log, FPS drop, stuttering, freeze, performance, won't start, 崩溃, 掉帧, 卡顿 symptoms and the user needs a symptom-first diagnostic ladder. NOT for proactive post-install testing; use testing-bgs-modpack.
using-bgs-archive
Use when the user wants to inspect, list, extract, unpack, or repack Bethesda BA2/BSA archives; determine archive format/version/compression; or build archive assets for an MO2 overlay. Triggers - "unpack BA2", "extract BSA", "pack archive", "inspect archive", "bgs-archive".
running-julia-test
Before running tests for a new package, make sure the test environment is already set up. If the package does not have tests yet, follow creating-julia-test-env first. Tests that use using Test must have Test available from the package or test project.
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.