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/statusgit 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/status)<a href="https://agentmods.dev/rules/votruongdanh/skills-agent/status"><img src="https://agentmods.dev/badge/rules/votruongdanh/skills-agent/status.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.00051 | $0.00673 |
| Opus 5 | $0.00026 | $0.00336 |
| Sonnet 5 | $0.00010 | $0.00135 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
status 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 — 65 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. This is the PRIMARY source for status — check all recorded history, decisions, tasks, bugs, and milestones.
END: Update .ai-memory.md using Memory Compaction Rules with: status snapshot, what's working, gaps, risks, and priorities.
Goal
Summarize where things stand right now, leveraging the memory file for deep context.
Agent Routing
- For project health overview → read
.kiro/skills/agents/agents/project-planner.mdand apply its knowledge - For multi-workstream status → read
.kiro/skills/agents/agents/orchestrator.mdand apply its knowledge - For technical debt assessment → read the relevant specialist agent file based on domain
Workflow
- Read Memory — Load
.ai-memory.mdas the primary context source. - Inspect the repository, relevant files, and any recent context from the chat.
- Summarize what already exists.
- Identify gaps, risks, TODOs, and likely next priorities.
- Present a concise health/status view.
- Update Memory — Save current status snapshot to
.ai-memory.md.
Output format
- Current state (from memory + repo scan)
- What is working
- What is incomplete
- Risks or blockers
- Recent changes (from memory)
- Recommended next step
Checklist
-
Memory file read for historical context
-
Repository scanned for current state
-
Working features identified
-
Gaps and incomplete items listed
-
Risks or blockers flagged
-
Next priority recommended
-
Memory file updated with status snapshot
-
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
- Be specific and evidence-based.
- Separate facts from inference.
- Do not recommend broad refactors without confirming scope; ASK if the fix would touch many areas.
- Always read and update the memory file.
Quality Gate
After completing, read .kiro/skills/_scripts/verify-all.md for full project verification checklist.
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 9b7c825fbcc1
- 5d ago First seen · 62 lines · 51 tokens per session scan A 09e4f3f711ab
status is a cursor rule published in the GitHub repository VoTruongDanh/Skills-Agent (2 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 673 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-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.