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 rules/votruongdanh/skills-agent/previewgit clone --depth 1 https://github.com/VoTruongDanh/Skills-AgentWrote 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/votruongdanh/skills-agent/preview)<a href="https://agentmods.dev/rules/votruongdanh/skills-agent/preview"><img src="https://agentmods.dev/badge/rules/votruongdanh/skills-agent/preview.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 | $0.00052 | $0.00728 |
| Opus 5 | $0.00026 | $0.00364 |
| Sonnet 5 | $0.00010 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
preview 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 today.
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Protocol
START: Read .ai-memory.md from project root. Check UI patterns, design decisions, existing previews, brand guidelines, and user flow notes.
END: Update .ai-memory.md using Memory Compaction Rules with: what was previewed, assumptions, feedback, and confirmed decisions.
Goal
Show the user what the result will look or feel like before full implementation.
Agent Routing
- If previewing UI/UX → read
.kiro/skills/agents/agents/frontend-specialist.mdand apply its knowledge - If previewing documentation → read
.kiro/skills/agents/agents/documentation-writer.mdand apply its knowledge - If previewing API response → read
.kiro/skills/agents/agents/backend-specialist.mdand apply its knowledge
Socratic Gate
Before previewing, verify:
- What artifact is being previewed? (UI, API output, document, flow?)
- What level of fidelity is expected? (wireframe, mockup, full sample?)
- Any specific requirements or constraints? If any answer is unclear, ASK before proceeding.
Workflow
- Read Memory — Load
.ai-memory.mdfor project context and design history. - Infer the artifact being previewed: UI, API output, document, message, workflow, or report.
- Produce a faithful mock, sample output, walkthrough, or structured preview.
- Highlight assumptions behind the preview.
- Identify what could change during implementation.
- Update Memory — Save preview details and decisions to
.ai-memory.md.
Checklist
-
Artifact type identified
-
Preview is realistic and faithful
-
Assumptions clearly labeled
-
Mock data marked as illustrative
-
Implementation differences noted
-
Memory file updated
-
Clean code chuẩn (Standard clean code applied)
-
Cập nhật đầy đủ tất cả các file liên quan (All related files fully updated)
Rules
- Keep previews realistic and consistent with the current project.
- Label illustrative content clearly when it is mock data.
- Avoid implying broad code changes; if the preview would require major refactor, CALL IT OUT and ASK before implementation.
- Always read and update the memory file.
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.
- today Changed · +3 lines b5274d367f82
- 5d ago First seen · 60 lines · 52 tokens per session scan A 1d488adb596e
preview is a cursor rule published in the GitHub repository VoTruongDanh/Skills-Agent (2 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 728 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.