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 instructions/consenlabs/token-ui/agents-mdgit clone --depth 1 https://github.com/consenlabs/token-uiWhat 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.00937 | $0.00937 |
| Opus 5 | $0.00468 | $0.00468 |
| Sonnet 5 | $0.00187 | $0.00187 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade B, and why
token-ui AGENTS.md scanned grade B with 2 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
`curl | sh`-style installers from agent actions. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl | sh`-style installers from agent actions. How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Working Agreement
- Read the closest relevant files before editing, then make the smallest focused change that solves the request.
- Prefer existing local patterns, components, and tokens over new abstractions or dependencies.
- Ask or propose a short plan when requirements are ambiguous, architectural, or likely to touch several areas.
UI Implementation Protocol
- Before building or changing UI, read
DESIGN.mdand treat it as the source of truth for visual style, typography, spacing, radius, color roles, motion, and responsive behavior. - Prefer components from
@repo/ui/components/*and tokens from@repo/ui/globals.cssbefore creating app-level styles or new components. - Import global styles once from
@repo/ui/globals.css; do not duplicate design tokens in app-level CSS.
Commands
- Use the existing pnpm workspace; do not switch package managers.
- After substantive code changes, run
pnpm verify. - For quick checks, run at least
pnpm checkandpnpm typecheck. - For web-only feedback, prefer scoped commands such as
pnpm --filter @repo/web testorpnpm --filter @repo/web typecheck. - Do not install dependencies, push, delete files, or run destructive git commands without explicit user approval.
Security Protocol
This repository is a wallet UI starter kit for public co-creation. It may include wallet-like user flows, but security-sensitive behavior must be handled explicitly and conservatively.
What is in scope
- UI flows for wallet creation, import, account display, send/receive, signing preview, token approval warnings, DApp connection, and other wallet-related interactions are allowed.
- Mock data, test wallets, local-only demos, and testnet-oriented integrations are preferred during development and examples.
- If a feature touches real signing or chain interaction, make the risk visible in the UI and keep the implementation narrowly scoped to the user's request.
Secrets (private keys, mnemonics, passwords)
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 · 100 lines · 937 tokens per session scan B 31b8ee49320f
token-ui AGENTS.md is an instructions file published in the GitHub repository consenlabs/token-ui (5 stars, last pushed 1mo ago), licensed MIT. It adds 937 tokens to every session, about $0.0047 per session on Opus 5. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.