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/ui-linksnpx skills add wecode-ai/Wegent --skill ui-linksgit clone --depth 1 https://github.com/wecode-ai/WegentWrote 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/wecode-ai/wegent/ui-links)<a href="https://agentmods.dev/skills/wecode-ai/wegent/ui-links"><img src="https://agentmods.dev/badge/skills/wecode-ai/wegent/ui-links.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.1 | $0.00048 | $0.01668 |
| Opus 5 | $0.00024 | $0.00834 |
| Sonnet 5 | $0.00010 | $0.00334 |
| Haiku 4.5 | $0.00005 | $0.00167 |
Grade A, and why
ui-links 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 6d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Links
This skill enables you to output special protocol links that the Wegent frontend renders as interactive elements. Use these links to display attachments or provide navigation to Wegent pages.
When to Use
Use this skill when:
- User asks to "show", "view", "display", or "open" an attachment (image, file, etc.)
- User wants to navigate to a specific Wegent page (settings, chat, knowledge base, etc.)
- User needs quick actions like creating tasks, sending messages, or exporting data
- You need to provide clickable navigation within your response
Important: You do NOT need to call any tools. Simply output the markdown links directly in your response.
Protocol Reference
1. Attachment Protocol (attachment://)
Display attachments (images, files) that exist in the conversation.
Format:
Parameters:
ID(required): The numeric attachment ID (positive integer)
Example:
How it works:
- The frontend automatically renders the attachment as a clickable preview
- For images: displays an inline preview that can be expanded
- For files: displays a file card with download option
2. Wegent Protocol (wegent://)
Navigate to Wegent pages or trigger actions.
Format:
[link text](wegent://type/path?params)
Structure:
type: Category of operation (open,form,action)path: Specific target within the typeparams: Optional query parameters
Available Routes
Navigation Routes (wegent://open/*)
Open Wegent pages directly.
| Route | Description | Parameters |
|---|---|---|
wegent://open/chat |
Open chat page | team (optional): Team ID |
wegent://open/code |
Open code page | team (optional): Team ID |
wegent://open/settings |
Open settings page | tab (optional): integrations, bot, team, models |
wegent://open/knowledge |
Open knowledge base | Path parameter for project ID |
wegent://open/feed |
Open activity feed | None |
wegent://open/feedback |
Open feedback dialog | None |
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.
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.
- 6d ago First seen · 221 lines · 48 tokens per session scan A a7356e291422
ui-links is a skill published in the GitHub repository wecode-ai/Wegent (782 stars, last pushed today), licensed Apache-2.0. It adds 48 tokens to every session and 1,668 once invoked, about $0.0002 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
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…
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…
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.
bluebubbles
Handles sending and managing iMessages through BlueBubbles, the recommended iMessage integration. Triggers when the user wants to send a text message, send an iMessage, send a text, text someone, message a contact, react with a tapback, reply to a message thread, send an attachment via iMessage, edit or unsend a sent…