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/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/create)<a href="https://agentmods.dev/rules/votruongdanh/skills-agent/create"><img src="https://agentmods.dev/badge/rules/votruongdanh/skills-agent/create/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/votruongdanh/skills-agent/create"><img src="https://agentmods.dev/badge/rules/votruongdanh/skills-agent/create.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.00053 | $0.00822 |
| Opus 5.5 | $0.00021 | $0.00329 |
| Sonnet 5.5 | $0.00011 | $0.00164 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
create 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 1mo 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 — 71 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 tech stack, coding conventions, existing patterns, architecture decisions, and file structure notes.
END: Update .ai-memory.md using Memory Compaction Rules with: what was created, files touched, patterns used, decisions, and follow-ups.
Goal
Create a new implementation cleanly and with minimal disruption.
Agent Routing
- If creating API/backend → read
.kiro/skills/agents/agents/backend-specialist.mdand apply its knowledge - If creating UI component/page → read
.kiro/skills/agents/agents/frontend-specialist.mdand apply its knowledge - If creating database schema/migration → read
.kiro/skills/agents/agents/database-architect.mdand apply its knowledge - If creating tests → read
.kiro/skills/agents/agents/test-engineer.mdand apply its knowledge - If creating deployment config → read
.kiro/skills/agents/agents/devops-engineer.mdand apply its knowledge
Socratic Gate
Before creating, verify:
- What exactly should be created? (component, page, API, script?)
- Does something similar already exist in the project?
- What is the expected behavior/output? If any answer is unclear, ASK before proceeding.
Workflow
- Read Memory — Load
.ai-memory.mdfor project context, conventions, and patterns. - Understand the requested artifact and the existing project structure.
- Identify the smallest complete implementation that satisfies the request.
- Create or update the necessary files only.
- Reuse existing patterns, naming, and architecture already present in the repo.
- Include basic validation and error handling.
- Add brief usage notes, edge cases, and follow-up improvements.
- Update Memory — Save what was created, patterns used, and follow-up notes to
.ai-memory.md.
Checklist
- Requirement clearly understood
- Existing patterns/conventions checked
- Minimal files created/modified
- Validation and error handling included
- Project conventions matched (naming, structure)
- Tests added if test framework exists
- Usage notes provided
- Memory file updated
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.
- 1mo ago Changed · +3 lines a4abe5e92f13
- 1mo ago First seen · 68 lines · 53 tokens per session scan A 1e7e02729618
create is a cursor rule published in the GitHub repository VoTruongDanh/Skills-Agent (4 stars, last pushed 18d ago), licensed MIT. It adds 53 tokens to every session and 822 once invoked, about $0.0002 per session on Opus 5.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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).