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 skills add crevideo/crevideo-reach --skill creator-tier-resolvergit clone --depth 1 https://github.com/crevideo/crevideo-reachWrote 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/crevideo/crevideo-reach/creator-tier-resolver)<a href="https://agentmods.dev/skills/crevideo/crevideo-reach/creator-tier-resolver"><img src="https://agentmods.dev/badge/skills/crevideo/crevideo-reach/creator-tier-resolver/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/crevideo/crevideo-reach/creator-tier-resolver"><img src="https://agentmods.dev/badge/skills/crevideo/crevideo-reach/creator-tier-resolver.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.00108 | $0.01011 |
| Opus 5 | $0.00054 | $0.00505 |
| Sonnet 5 | $0.00022 | $0.00202 |
| Haiku 4.5 | $0.00011 | $0.00101 |
Grade A, and why
creator-tier-resolver 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 11d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creator Tier Resolver · 达人分级判定
Role: answer only "which tier this creator should be in, and whether they hit the graduation line". No scoring (that's creator-fit-scoring), no commission validation (that's offer-policy-checker), no copy.
Output language
Write every output in the merchant's working language, using that market's native seller terminology:
- US Local sellers → English: tier / all-in take-rate / outreach waterfall / Target Collaboration / DM / sample / graduation …
- China POP sellers → 中文: 分级 / 真实抽成 / 触达阶梯 / 定向邀约 / 私信 / 寄样 / 毕业 … Tool names stay identical in both languages. If unsure which market, ask once before producing output.
When to use / not use
- Use: set a creator's priority tier, judge Open→Target graduation, fix the tier for downstream offer/outreach.
- Don't use: fit not yet judged (run creator-fit-scoring first).
Inputs
- Creator evidence: conversion / GMV-per-view, orders, fulfillment, audience persona; follower count (reference only).
- Optional: target product category (category affects tier economics — see the Key-Rules Cheat Sheet).
Steps (in order)
- Hard-exclude check: blocklist / explicit opt-out / risk-signal hit → "Excluded / do not invite".
- Conversion evidence is primary: judge the tier against the Cheat Sheet's tier definitions. Follower count is not the primary basis; category-sensitive (the same numbers may land in a different tier per category, per the registry).
- Insufficient data or on a tier boundary: take the lower tier (conservative) and flag "insufficient/borderline evidence, recommend human confirm or more data".
- Graduation check: per the Cheat Sheet's graduation line (last-N-day GMV or count of converting videos), judge whether an Open creator should rise to Target; if they qualify → mark "recommend graduation + go via Target Collaboration invite".
- Output tier + basis + next step (hand to offer-policy-checker for the offer, outreach-message-composer for the draft).
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.
- 11d ago First seen · 63 lines · 108 tokens per session scan A 386796d2e8bf
creator-tier-resolver is a skill published in the GitHub repository crevideo/crevideo-reach (7 stars, last pushed 3d ago), licensed MIT. It adds 108 tokens to every session and 1,011 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
markifact-overview
Reference — what Markifact is, what the MCP server exposes, and the discover→inspect→run pattern. Always loaded into the performance-marketer agent.
safe-write-operations
Reference — rules for safely executing write/destructive operations against ad accounts. Always loaded into the performance-marketer agent.
dev
Software development planning. Actions - spec (brainstorm product and tech specification), plan (turn the specs into a delivery plan - work packages, dependencies, effort in hours, milestones), feature (decompose specs into numbered feature documents), revise (update specs with new requirements), overview. Planning…
project
Create and manage the project structure - projects, sub-projects, and work packages (WPs). Actions - new project, new subproject, new WP, overview. Hierarchy depth (2 or 3 levels) is fixed at creation. All work happens in WPs; projects and sub-projects are pure structure.
ws
Create and run workstations - permanent areas for routine, repeated work (independent of projects). Actions - new WS, new subWS, new area, new routine, run, from project, list, overview. Hierarchy depth (2 or 3 levels) is fixed at creation.
cease-desist
Draft a cease-and-desist letter (send mode) or triage one you received (receive mode). Use when asserting your rights against an infringer with a demand letter calibrated to your enforcement posture, or when an incoming C&D needs triage into a structured options memo with a recommendation.