manage-waitlist

manage-waitlist is a skill for Claude Code, Codex from Rabithua/FeedbackServerPlugin. It costs 61 tokens per session (463 once invoked), scanned A, original, MIT.

A tool for managing waitlists, which are lists of people who signed up for early access to an app or service.

In plain words
What is it for?
Use it to find signups, add notes, change statuses, archive or delete entries, and send or retry invitations.
Why use it?
It keeps signup follow-up organized and separates ordinary status changes from invitations and permanent deletion.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the feedback-server plugin — 7 skills shipped together

Good fit Use it to find signups, add notes, change statuses, archive or delete entries, and send or retry invitations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rabithua/feedbackserverplugin/manage-waitlist
Install

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.

Any agent
npx skills add Rabithua/FeedbackServerPlugin --skill manage-waitlist
Clone the repo
git clone --depth 1 https://github.com/Rabithua/FeedbackServerPlugin

Made for: Claude Code, Codex.

Or install feedback-server, the plugin that ships this one along with the rest of its 7 skills.

Wrote 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.

agentmods badge for manage-waitlist

README.md
[![agentmods](https://agentmods.dev/badge/skills/rabithua/feedbackserverplugin/manage-waitlist/github.svg)](https://agentmods.dev/skills/rabithua/feedbackserverplugin/manage-waitlist)
Your own site
<a href="https://agentmods.dev/skills/rabithua/feedbackserverplugin/manage-waitlist"><img src="https://agentmods.dev/badge/skills/rabithua/feedbackserverplugin/manage-waitlist/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.

agentmods 80×15 button for manage-waitlist

Your own site · 80×15
<a href="https://agentmods.dev/skills/rabithua/feedbackserverplugin/manage-waitlist"><img src="https://agentmods.dev/badge/skills/rabithua/feedbackserverplugin/manage-waitlist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 463 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.00463
Opus 5.5 $0.00024 $0.00185
Sonnet 5.5 $0.00012 $0.00093
Haiku 4.5 $0.00006 $0.00046

Measured 2mo ago against content hash 59cbe8c70877, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

manage-waitlist 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 2mo 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.

plugins/feedback-server/skills/manage-waitlist/SKILL.md · 32 lines

What it actually says

Manage the FeedbackServer 2.0 waitlist

Waitlist entries belong to the connected administrator and are not Product-scoped. Do not ask for a Product. Use list_waitlist_entries and get_waitlist_entry, apply status, platform, and search filters, and follow nextCursor. Archived entries are hidden unless explicitly requested. Treat email as private contact data and include it only when the task needs it.

update_waitlist_status and add_waitlist_note are direct internal writes after resolving the exact entry. Valid statuses are new, contacted, invited, converted, and archived. Do not substitute archive for a requested permanent deletion or vice versa.

Invitation email is a protected external effect. invite_waitlist_entry requires an exact recipient, language, App, subscription grant, and expiry. Free needs no term; Solo and Studio require an explicit month, year, or perpetual term. Never infer one. Use the same protection for retry_invitation_email; use revoke_invitation to cancel a pending invitation before deleting a blocked signup. Revocation cannot recall mail already accepted by the provider.

The invitation recipient's Agent workflow consumes only mcp_server and account_email. The user signs in as that email through the browser magic-link flow, then the Agent verifies the account with whoami. Do not ask for a username, display name, password, emailed link, or any additional invitation credential.

For invitations, retries, revocation, and delete_waitlist_entry, prefer native MCP elicitation. If the client cannot elicit and the tool returns confirmation_required, show the exact redacted effect, wait for approval, then repeat the same tool with identical arguments plus confirm: true. Never use a confirmation identifier. Reread state after a conflict and never retry a mutation automatically.

Files

What ships with it

1 file 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.

Changes

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.

  1. 2mo ago Changed · -8 lines · +6 tokens per session 59cbe8c70877
  2. 2mo ago First seen · 40 lines · 55 tokens per session scan A 82f68d48eca3

Subscribe to this mod's changes

manage-waitlist is a skill published in the GitHub repository Rabithua/FeedbackServerPlugin (0 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 463 once invoked, about $0.0002 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-08-31.

Related

manage-waitlist compared with skills from other repositories

manage-waitlist next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
manage-waitlistRabithua/FeedbackServerPluginSkill02mo agoMITA61Claude Code, Codex
johari-windowfatihguner/foremanSkill632mo agoMITA105Claude Code
leader-self-reflectionfatihguner/foremanSkill632mo agoMITA113Claude Code
run-underperformance-conversationjeffreytse/grimoire-coreSkill61mo agoMITA54Claude Code
run-difficult-conversationjeffreytse/grimoire-coreSkill61mo agoMITA29Claude Code
run-one-on-onejeffreytse/grimoire-coreSkill61mo agoMITA23Claude Code
weekly-stop-itemace3000chao/book2startupSkill986mo agoMITA77Claude Code, Codex