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 skills add kieutrongthien/skills-fullstack --skill plan-agile-developmentgit clone --depth 1 https://github.com/kieutrongthien/skills-fullstackWrote 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/kieutrongthien/skills-fullstack/plan-agile-development)<a href="https://agentmods.dev/skills/kieutrongthien/skills-fullstack/plan-agile-development"><img src="https://agentmods.dev/badge/skills/kieutrongthien/skills-fullstack/plan-agile-development/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/kieutrongthien/skills-fullstack/plan-agile-development"><img src="https://agentmods.dev/badge/skills/kieutrongthien/skills-fullstack/plan-agile-development.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.00018 | $0.00632 |
| Opus 5 | $0.00009 | $0.00316 |
| Sonnet 5 | $0.00004 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
plan-agile-development 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 10d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agile Development Execution Skill
What it does
- Guides dev tasks from acceptance criteria to code, tests, PRs, and status updates.
- Ensures branch/PR hygiene and continuous integration checks stay green.
When to use
- When breaking a story into tasks and coding steps.
- While monitoring day-to-day execution, task movement, and CI health.
Key operations
- Identify active project; read
PROJECT.md,current-sprint.json,tasks/todo.json. - Task breakdown: story → tasks/subtasks; assign owners; set branch/PR naming.
- Status transitions: move tasks between todo → in-progress → in-review/testing → done; log time/blockers.
- CI hygiene: run lint/test/build locally; keep pipelines green; record notable CI runs.
- Progress tracking: update task-plan and dev-notes; re-plan if blocked; log to
memory/YYYY-MM-DD.md.
Output files
projects/<ACTIVE>/tasks/todo.json— tasks not started.projects/<ACTIVE>/tasks/in-progress.json— active tasks.projects/<ACTIVE>/tasks/done.json— completed tasks.projects/<ACTIVE>/tasks/task-log.md— daily progress/time/blockers.execution/task-plan.md— per-story task breakdown (if used locally).execution/dev-notes.md— decisions, trade-offs, blockers, follow-ups.execution/ci-status.md— notable CI runs, failures, fixes, flaky tests.memory/YYYY-MM-DD.md— session decisions, blockers, time spent.
Example workflow
- Pull story details; restate acceptance criteria; break into tasks; assign owners.
- Move task to
in-progress.json; create branch; code with small commits; run lint/test/build before PR. - Update
task-plan.md/dev-notes.md; track CI runs inci-status.md; log blockers intask-log.mdandmemory/YYYY-MM-DD.md. - Move task to
in-review.json/testing.jsonthendone.json; ensure statuses and logs updated.
Best practices (best practice)
- Keep PRs small and focused; link to story ID.
- Automate checks locally (pre-commit/dev-check scripts) before pushing.
- Communicate blockers within same day; avoid silent stuck work.
- Keep tasks visible; update statuses daily across
todo.json/in-progress.json/done.json. - Log hours/time spent for velocity and capacity accuracy.
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.
- 10d ago First seen · 50 lines · 18 tokens per session scan A a7f1121c7103
plan-agile-development is a skill published in the GitHub repository kieutrongthien/skills-fullstack (2 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 632 once invoked, about $0.0001 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.