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 skills/phuoctrung-ppt/ai-sdlc-workflow/agentic-workflownpx skills add phuoctrung-ppt/ai-sdlc-workflow --skill agentic-workflowgit clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-workflowWrote 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/phuoctrung-ppt/ai-sdlc-workflow/agentic-workflow)<a href="https://agentmods.dev/skills/phuoctrung-ppt/ai-sdlc-workflow/agentic-workflow"><img src="https://agentmods.dev/badge/skills/phuoctrung-ppt/ai-sdlc-workflow/agentic-workflow.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.00039 | $0.01111 |
| Opus 5 | $0.00019 | $0.00556 |
| Sonnet 5 | $0.00008 | $0.00222 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
agentic-workflow 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Workflow
This skill is repo/domain agnostic. Project-specific context (name, tech stack, paths, compliance) lives in AGENTS.md and .cursor/config/*.json. This skill explains the workflow mechanics only.
Core Loop (V2)
- Classify —
.cursor/config/protected-paths.json - Context —
python3 .cursor/context/context-builder.py --task "..." --agent <agent> - Plan — protected/multi-module →
docs/plans/YYYY-MM-DD-topic.md(compact) - Execute — narrowest worker; obey Context Packet tiers
- Verify — checks proportional to risk
- Review — protected →
docs/reviews/; extract reusable patterns to.cursor/patterns/
Context Builder (V2)
Primary entry (replaces direct skill-loader calls):
python3 .cursor/context/context-builder.py \
--task "<description>" \
--agent <agent-id> \
[--paths path1,path2] \
[--keywords kw1,kw2] \
[--handoff docs/plans/.active-plan] \
[--budget 8000]
Lazy reference expansion:
python3 .cursor/context/context-builder.py --expand-ref "<path>" --reason "<why>"
Sync project memory after AGENTS.md changes:
python3 .cursor/context/memory-loader.py --sync
Legacy: --use-legacy-loader delegates to skill-loader.py.
Handoff Packet
Every worker task starts from a handoff packet. Fill this before dispatching:
Objective:
In-scope paths:
Out-of-scope paths:
Plan/ADR:
Required skills:
Acceptance criteria:
Required verification:
Risk notes:
Scope expansion path:
Agent Roster
See AGENTS.md §4 for the full agent table for this project. Standard agents available in .cursor/agents/:
| Agent | Role |
|---|---|
architect-planner |
Plans, writes ADRs, dispatches handoff packets |
scaffold-agent |
Bootstraps module/page shells before workers implement |
designer-worker |
UI/UX design, component specs, design systems |
backend-worker |
API features, services, DTOs |
frontend-worker |
UI components, pages, data fetching |
database-worker |
Migrations, schema design, query optimization |
ai-worker |
LLM integration, embeddings, cost tracking |
devops-worker |
Docker, CI/CD, infra |
security-worker |
Auth, RBAC, encryption, compliance |
qa-worker |
Tests: unit, integration, E2E |
judge-agent |
Read-only review gate |
admin-worker |
Admin/control-plane (elevated privilege) |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 117 lines · 39 tokens per session scan A c896a97a5872
agentic-workflow is a skill published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 19d ago), licensed MIT. It adds 39 tokens to every session and 1,111 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…