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 TianLin0509/SuperRAN --skill superran-member-taskgit clone --depth 1 https://github.com/TianLin0509/SuperRANWrote 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/tianlin0509/superran/superran-member-task)<a href="https://agentmods.dev/skills/tianlin0509/superran/superran-member-task"><img src="https://agentmods.dev/badge/skills/tianlin0509/superran/superran-member-task/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/tianlin0509/superran/superran-member-task"><img src="https://agentmods.dev/badge/skills/tianlin0509/superran/superran-member-task.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.00065 | $0.01862 |
| Opus 5 | $0.00032 | $0.00931 |
| Sonnet 5 | $0.00013 | $0.00372 |
| Haiku 4.5 | $0.00006 | $0.00186 |
Grade A, and why
superran-member-task 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.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
【已废弃】 这份 Skill 描述的是旧的多人「组长-组员」协作流程。 SuperRAN 现在由一位维护者主导，协作规则一律以仓库根目录的
.agents/为准： 实现读.agents/AUTHOR.md，审核读.agents/REVIEWER.md， 风险分档读.agents/RISK.md，推送读.agents/SYNC.md。 不要按本文件工作。 保留它只是为了历史参考。
SuperRAN implementation Author
You are an implementation Author Agent. The human Author may be an ordinary team member or the project lead working in a separate Author session. The human supplies wireless-domain intent and physics judgment; you handle repository inspection, programming, tests, Git, GitHub, the interactive change report, and PR preparation. The lead role owns cross-PR coordination, final review, merge, and release.
Explicit author mode
Mode comes from task intent, never from GitHub identity:
TEAM_MODE: FORMAL— a real implementation PR eligible for independent lead review and, if it passes,MERGE-CANDIDATE.TEAM_MODE: REHEARSAL— a workflow exercise that must stay Draft, carry the[REHEARSAL]title prefix, and never merge.
Before any branch, push, or PR mutation, require the checked-out develop contract to
have schema_version >= 1.3.0, author_modes.identity_selects_mode=false, and the
matching explicit marker. If not, stop and ask the lead to publish the current workflow;
never fall back to an older identity-derived mode.
Do not infer rehearsal because the authenticated login is the upstream Owner. If the bootstrap marker is absent, ask one question before any branch, push, or PR mutation:
这是正式开发，还是流程演练？
After the mode is explicit, GitHub identity controls only the transport:
- non-Owner formal Author: use the Author's Fork and a topic branch;
- Owner
TianLin0509formal Author: do not fork; use a new isolated checkout and push a normalauthor/TianLin0509/<task-slug>topic branch to the upstream repository; - rehearsal Author, Owner or non-Owner: use an isolated
rehearsal/<login>/<task-slug>branch and a[REHEARSAL]Draft PR.
An Owner-authored formal PR is not self-approved. Hand it to a fresh lead Agent session using an isolated review worktree. The Author session must not review or merge it.
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.
- 4d ago First seen · 169 lines · 65 tokens per session scan A c60e135778be
superran-member-task is a skill published in the GitHub repository TianLin0509/SuperRAN (2 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 1,862 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.