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/instructionsgit 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/instructions)<a href="https://agentmods.dev/rules/votruongdanh/skills-agent/instructions"><img src="https://agentmods.dev/badge/rules/votruongdanh/skills-agent/instructions.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.01584 | $0.01584 |
| Opus 5 | $0.00792 | $0.00792 |
| Sonnet 5 | $0.00317 | $0.00317 |
| Haiku 4.5 | $0.00158 | $0.00158 |
Grade A, and why
instructions 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 5d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Skills — System Bootstrap
This project uses an AI Skills system with 16 skills, 11 specialist agents, and a memory protocol.
On EVERY request, follow this flow:
-
Validate input:
- If the message is empty or contains no meaningful content → Respond with a friendly greeting, list the available skills below with one-line descriptions, and ask what the user would like to work on. Do NOT proceed to classification.
- If the message is a greeting ("hi", "hello", "hey", "xin chào", "chào") → Respond warmly, briefly list what you can help with (the skills below), and ask how you can help. Do NOT proceed to classification.
-
Read memory:
- If
.ai-memory.mdexists in project root, read it first for context. - If Codex memory directories exist (
memories/,memories/session/,memories/repo/), read relevant notes frommemories/repo/. - If
.ai-memory.mddoesn't exist, create it after completing the first task using the template at the end of this file.
- If
-
Classify the request — Match to one of these skills:
Command Skill file to read When to use /brainstorm.kiro/skills/brainstorm/SKILL.mdExplore options, ideate solutions /plan.kiro/skills/plan/SKILL.mdCreate implementation plan with milestones /create.kiro/skills/create/SKILL.mdBuild new feature/file/component /debug.kiro/skills/debug/SKILL.mdFix bugs, analyze errors /test.kiro/skills/test/SKILL.mdWrite tests, improve coverage /enhance.kiro/skills/enhance/SKILL.mdImprove existing code without breaking it /deploy.kiro/skills/deploy/SKILL.mdDeployment and release guidance /clean.kiro/skills/clean/SKILL.mdRemove junk files, clean up /status.kiro/skills/status/SKILL.mdProject status summary /preview.kiro/skills/preview/SKILL.mdPreview output/UX before implementing /orchestrate.kiro/skills/orchestrate/SKILL.mdCoordinate multi-step workflows /ui-ux-pro-max.kiro/skills/ui-ux-pro-max/SKILL.mdAdvanced UI/UX improvements /motion-ui.kiro/skills/motion-ui/SKILL.mdMotion UI with Framer Motion micro-interactions /explain.kiro/skills/explain/SKILL.mdExplain code, walk through logic, understand architecture /integrate.kiro/skills/integrate/SKILL.mdIntegrate provided sample code with minimal impact
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.
- 5d ago First seen · 103 lines · 1,584 tokens per session scan A bf5963368bdc
instructions is a cursor rule published in the GitHub repository VoTruongDanh/Skills-Agent (2 stars, last pushed yesterday), licensed MIT. It adds 1,584 tokens to every session, about $0.0079 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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-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.