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/wecode-ai/wegent/interactivenpx skills add wecode-ai/Wegent --skill interactivegit clone --depth 1 https://github.com/wecode-ai/WegentWhat 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.00059 | $0.01318 |
| Opus 5 | $0.00030 | $0.00659 |
| Sonnet 5 | $0.00012 | $0.00264 |
| Haiku 4.5 | $0.00006 | $0.00132 |
Grade A, and why
interactive 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 2d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask User
You now have access to the interactive_form_question tool. Use it to ask the user questions during execution.
When to Use
- Gather user preferences or requirements — before starting or when more detail is needed
- Clarify ambiguous instructions — when the request could be interpreted multiple ways
- Get decisions on implementation choices as you work — when a fork in the road requires user input
- Offer choices on direction — let the user steer when multiple valid paths exist
- Present any list of options to the user — whenever you would naturally write a numbered/bulleted list of choices for the user to pick from, use
interactive_form_questioninstead
Never write options, choices, or questions as plain text or markdown lists — always call the tool.
Usage Notes
- Users can always select "Other" to provide custom text input, even on choice questions — you don't need to add it manually
- Use
multi_select: trueto allow multiple answers to be selected - If you recommend a specific option, set
"recommended": trueon that option — the frontend will display the recommended badge automatically. NEVER add "(Recommended)", "(推荐)" or any similar text to thelabelfield — the badge is rendered by the frontend, not by text in the label - Always pass questions via
questions=[...]. A single-question form is just a one-itemquestionsarray. - After receiving answers, call
interactive_form_questionagain if follow-up questions arise — never ask in plain text
Behavior
interactive_form_question displays an interactive form and returns immediately . The current task ends silently and resumes when the user submits their answer as a new message.
Tool Parameters
questions(list, required): The full list of questions to render- Each item in
questionshas:id: Unique identifierquestion: Question text shown to the userinput_type:"choice"or"text"options(optional):[{label, value, recommended?}]for choice questionsmulti_select(optional): Allow multiple selections; defaultfalserequired(optional): Whether the question must be answered; defaulttruedefault(optional): Pre-selected valuesplaceholder(optional): Placeholder for text input
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.
- 2d ago First seen · 159 lines · 59 tokens per session scan A 1331c4d20b0c
interactive is a skill published in the GitHub repository wecode-ai/Wegent (747 stars, last pushed 2d ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,318 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-08-30.
Other skills, from other repositories
build-monetized-app
Use when the task is building a new app on Eliza Cloud that earns money — chat apps, agent apps, MCP-backed tools, anything that calls the cloud's chat/messages/inference endpoints on behalf of users. Covers app registration, container deploy, markup configuration, affiliate header, app charge requests, x402 payment…
contribute-to-eliza
Finish and prove a scoped elizaOS GitHub issue, or independently review and repair an open elizaOS pull request. Use when contributing compute to elizaOS by selecting unclaimed work, implementing or reviewing changes, adding real tests and evidence, validating artifacts, or preparing a contribution for maintainer…
eliza-cloud
Use when the task involves Eliza Cloud or elizaOS Cloud as a managed backend, app platform, deployment target, billing layer, or monetization surface. The catch-all skill for any user request about THEIR existing apps / containers / earnings / credits / api-keys / analytics / billing / payment requests / payouts …
discord
Use when you need to control Discord from Otto via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, create/edit/delete channels and categories, fetch permissions or member/role/channel info, set bot presence/activity, or handle moderation actions in…
eliza-cloud-buy-domain
Use whenever a user wants to register or buy a custom domain for an Eliza Cloud app — including in the same request as building the app ("build me X and put it on Y.com"). Uses Cloudflare as registrar after explicit user confirmation, paid from the user's existing cloud credit balance. Pairs with build-monetized-app…
notion
Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.