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/testgit 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/test)<a href="https://agentmods.dev/rules/votruongdanh/skills-agent/test"><img src="https://agentmods.dev/badge/rules/votruongdanh/skills-agent/test.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.00058 | $0.00740 |
| Opus 5 | $0.00029 | $0.00370 |
| Sonnet 5 | $0.00012 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
test 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 4d 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 — 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 test framework in use, existing test coverage, known failing tests, testing patterns, and CI/CD test configuration.
END: Update .ai-memory.md using Memory Compaction Rules with: tests changed, coverage deltas (if known), patterns established, and gaps.
Goal
Improve confidence in the system through targeted testing.
Agent Routing
- Primary → read
.kiro/skills/agents/agents/test-engineer.mdand apply its knowledge - If testing reveals bugs → read
.kiro/skills/agents/agents/debugger.mdand apply its knowledge - For E2E/integration tests with UI → read
.kiro/skills/agents/agents/frontend-specialist.mdand apply its knowledge - For API/backend tests → read
.kiro/skills/agents/agents/backend-specialist.mdand apply its knowledge - For security testing → read
.kiro/skills/agents/agents/security-auditor.mdand apply its knowledge
Socratic Gate
Before writing tests, verify:
- What is the test scope? (unit, integration, E2E, API?)
- Does a test framework already exist in the project?
- What are the critical paths that must be tested? If any answer is unclear, ASK before proceeding.
Workflow
- Read Memory — Load
.ai-memory.mdfor testing history and patterns. - Identify the unit, integration, API, UI, or regression scope.
- Enumerate critical paths, edge cases, and failure modes.
- Add or propose tests that cover the most important risks first.
- Explain how to run the tests and what passing means.
- Quality Gate — Read
.kiro/skills/_scripts/checklist.mdand run test suite after writing tests. - Update Memory — Save test details and coverage notes to
.ai-memory.md.
Checklist
-
Test scope identified
-
Test framework confirmed/proposed
-
Critical paths covered
-
Edge cases included
-
Failure modes tested
-
Tests are stable (not brittle)
-
Run instructions provided
-
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)
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.
- 4d ago First seen · 63 lines · 58 tokens per session scan A aa2bccb2af92
test is a cursor rule published in the GitHub repository VoTruongDanh/Skills-Agent (2 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 740 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-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.
family-instance-domain-actions
Family instance domain action implementation patterns.