Borrowing it
Nothing to install: this file belongs to VoTruongDanh/Skills-Agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/VoTruongDanh/Skills-Agent/main/.agents/skills/plan/SKILL.mdgit 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/skills/votruongdanh/skills-agent/plan)<a href="https://agentmods.dev/skills/votruongdanh/skills-agent/plan"><img src="https://agentmods.dev/badge/skills/votruongdanh/skills-agent/plan/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/skills/votruongdanh/skills-agent/plan"><img src="https://agentmods.dev/badge/skills/votruongdanh/skills-agent/plan.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.00057 | $0.00802 |
| Opus 5 | $0.00028 | $0.00401 |
| Sonnet 5 | $0.00011 | $0.00160 |
| Haiku 4.5 | $0.00006 | $0.00080 |
Grade A, and why
plan 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 — 77 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 existing plans, milestones, project structure, tech stack, ongoing work, and past decisions.
END: Update .ai-memory.md using Memory Compaction Rules with: plan summary, phases/tasks, key risks, and first recommended action.
Goal
Turn a request into an actionable plan with clear phases and tasks.
Agent Routing
- For architecture planning → read
.kiro/skills/agents/agents/project-planner.mdand apply its knowledge - For multi-domain coordination → read
.kiro/skills/agents/agents/orchestrator.mdand apply its knowledge - For technical feasibility → read the relevant specialist agent file:
- Backend:
.kiro/skills/agents/agents/backend-specialist.md - Frontend:
.kiro/skills/agents/agents/frontend-specialist.md - Database:
.kiro/skills/agents/agents/database-architect.md
- Backend:
Socratic Gate
Before planning, verify:
- What is the desired outcome? (specific deliverable)
- What constraints exist? (time, resources, tech stack)
- What is already built vs needs to be built? If any answer is unclear, ASK before proceeding.
Workflow
- Read Memory — Load
.ai-memory.mdfor project context and history. - Define the objective and acceptance criteria.
- Break the work into phases and tasks.
- Note file areas, systems, or modules likely to change.
- Estimate complexity and highlight risky items.
- End with a recommended first task.
- Update Memory — Save plan details to
.ai-memory.md.
Output format
- Objective
- Acceptance criteria
- Phases (with tasks under each)
- File areas / modules affected
- Risks (with mitigation)
- Recommended first action
Checklist
-
Objective clearly stated
-
Acceptance criteria defined
-
Phases broken down
-
Tasks are specific and actionable
-
Complexity estimated per task
-
Risks identified with mitigation
-
First action recommended
-
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.
- 5d ago Changed · +3 lines 476e09637286
- 10d ago First seen · 74 lines · 57 tokens per session scan A 1127ffc7ccdb
plan is a skill published in the GitHub repository VoTruongDanh/Skills-Agent (2 stars, last pushed 6d ago), licensed MIT. It adds 57 tokens to every session and 802 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.