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.
git clone --depth 1 https://github.com/ypolon7kiy/akashiWrote 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/rules/ypolon7kiy/akashi/sidebar-webview-ui-ux)<a href="https://agentmods.dev/rules/ypolon7kiy/akashi/sidebar-webview-ui-ux"><img src="https://agentmods.dev/badge/rules/ypolon7kiy/akashi/sidebar-webview-ui-ux/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/rules/ypolon7kiy/akashi/sidebar-webview-ui-ux"><img src="https://agentmods.dev/badge/rules/ypolon7kiy/akashi/sidebar-webview-ui-ux.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.00000 | $0.00812 |
| Opus 5 | $0.00000 | $0.00406 |
| Sonnet 5 | $0.00000 | $0.00162 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
sidebar-webview-ui-ux 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 9d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Akashi Webview UI/UX Rule
Match the VS Code workbench: all webviews (activity-bar sidebar, editor panels, etc.) should use var(--vscode-*) theme variables so installed themes control colors and type—no separate “Akashi skin.” Shared tokens live in src/webview-shared/vscode-tokens.css; reuse webview-controls.css for buttons/progress.
- Typography: base UI on
var(--vscode-font-size)andvar(--vscode-font-family). Usevar(--vscode-descriptionForeground)(and font-weight) for secondary text; avoid ad-hoc11px/12pxscales unless expressed ascalc()from--vscode-font-sizewith a short comment rationale. - Emphasis: prefer weight (
font-weight: 600) over oversized display type. Prominent numbers may usecalc(var(--vscode-font-size) * 1.25)orvar(--vscode-editor-font-size)—pick one pattern per panel and stay consistent. - Surfaces: flat backgrounds from
--vscode-sideBar-*/--vscode-editorWidget-*; no gradients or heavy shadows. Border radius ~2–4px where corners are needed. - Lists / trees: use
--vscode-list-hoverBackground,--vscode-list-activeSelectionBackground/Foreground, and--vscode-list-focusBackground(with fallbacks) for interactive rows; align row height withvar(--vscode-font-size)plus padding. - Section blocks (e.g. “Indexed sources”): use
--vscode-sideBarSectionHeader-background,foreground, andborderwith fallbacks—Explorer-style headers, not isolated “cards.” - Buttons: map to
--vscode-button-*and--vscode-button-secondary*where available; keep states flat like workbench buttons. - Icons: use Codicons (
codicon codicon-…) for disclosure chevrons and other workbench-aligned glyphs when the font is loaded in the webview HTML. - Keep
--akashi-*only as thin aliases to--vscode-*when it improves readability; avoid hardcoded hex when a VS Code variable exists. - Keep spacing on an 8px rhythm (
4/8/12/16/20where needed for density). - Use consistent component states: idle, loading, success, error. Status labels must be explicit and short.
- Button hierarchy: one primary action per section, secondary actions visually quieter.
- During async work, disable conflicting controls and show clear progress text.
- Preserve accessibility: visible
:focus-visible, semantic labels, high-contrast support, and reduced-motion fallback. - Prefer CSS in dedicated files; avoid inline styles/scripts in webview HTML except unavoidable dynamic values.
- Keep sidebars uncluttered; prefer commands for actions that don’t belong in the panel.
- Verify dark, light, and high-contrast themes before finalizing UI 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.
- 9d ago First seen · 36 lines · 0 tokens per session scan A 2ccb7fa01633
sidebar-webview-ui-ux is a cursor rule published in the GitHub repository ypolon7kiy/akashi (3 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 812 tokens. 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.
Other cursor rules, from other repositories
external-scale
Source: docs/agents/external-scale.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
ui-motion-workflow
Orchestrate motion-aware UI work by sequencing direction, provider choice, implementation, and browser validation.
mobile-first-ui
Mobile-first UI for settings, dialogs, and lists — smaller type, stacked layouts, nested add dialogs.
frontend-design-direction
Derive a brief-specific visual direction, token sketch, hierarchy, and signature element.