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/integrategit 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/integrate)<a href="https://agentmods.dev/rules/votruongdanh/skills-agent/integrate"><img src="https://agentmods.dev/badge/rules/votruongdanh/skills-agent/integrate.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.00060 | $0.00716 |
| Opus 5 | $0.00030 | $0.00358 |
| Sonnet 5 | $0.00012 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
integrate 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 yesterday.
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 — 57 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. Focus on: entry points, key directories, conventions, and any integration decisions already logged.
END: Update .ai-memory.md using Memory Compaction Rules with: integration points, files touched, behavior changes (if any), and verification notes.
Goal
Merge the requested sample code into the current codebase without broad refactors, keeping behavior stable and avoiding changes to unrelated files.
Socratic Gate (ask if missing)
Before editing, verify these inputs exist. If any is missing or ambiguous, ASK:
- The sample code to integrate (full snippet + expected behavior).
- The target location in this project (file/module/feature area).
- Constraints: must keep API stable? must keep UI stable? backward compatible?
- 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 (Blast-radius control)
- Touch the smallest possible set of files.
- Do not reformat or restructure unrelated code.
- Prefer adapters/wrappers over rewriting existing modules.
- If the integration requires changing shared interfaces, introduce compatibility shims (or feature flag) instead of breaking changes.
- If uncertain about side effects, stop and ask rather than guessing.
Workflow
- Read Memory — Load
.ai-memory.mdfor architecture + conventions. - Locate Integration Point — Identify the narrowest place to hook in (entry, router, service, component, util).
- Diff the Concepts — Map sample code concepts → existing abstractions (types, services, routes, state).
- Design Minimal Bridge:
- Prefer adding a thin adapter layer rather than changing existing call sites.
- Prefer dependency injection/config wiring over global edits.
- Implement in Small Steps:
- Add new file(s) when that reduces risk (e.g.,
adapter/,integrations/). - Modify existing files only where the integration connects.
- Add new file(s) when that reduces risk (e.g.,
- Verification:
- Run/adjust existing tests if present; otherwise add a minimal smoke test when feasible.
- Ensure no unrelated behavior changes.
- Quality Gate — Read
.kiro/skills/_scripts/checklist.md. - Update Memory — Log only high-signal bullets (integration point, key decision, files touched, outcome).
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.
- yesterday Changed · +3 lines 9d94328e2234
- 6d ago First seen · 54 lines · 60 tokens per session scan A 86cee3d351f2
integrate is a cursor rule published in the GitHub repository VoTruongDanh/Skills-Agent (2 stars, last pushed 2d ago), licensed MIT. It adds 60 tokens to every session and 716 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
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-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.