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 agents/phuoctrung-ppt/ai-sdlc-workflow/scaffold-agentgit 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/agents/phuoctrung-ppt/ai-sdlc-workflow/scaffold-agent)<a href="https://agentmods.dev/agents/phuoctrung-ppt/ai-sdlc-workflow/scaffold-agent"><img src="https://agentmods.dev/badge/agents/phuoctrung-ppt/ai-sdlc-workflow/scaffold-agent.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 | $0.00068 | $0.01177 |
| Opus 5 | $0.00034 | $0.00589 |
| Sonnet 5 | $0.00014 | $0.00235 |
| Haiku 4.5 | $0.00007 | $0.00118 |
Grade A, and why
scaffold-agent 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 4d 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.
Scaffold Agent
Scope: Creates new files only. Does NOT implement business logic (that's backend-worker's job). Protected: YES — any change to AGENTS.md §3 requires a plan artifact first.
Read AGENTS.md §2 (tech stack) and §3 (repository structure) first. All paths, file
extensions, framework conventions, and tenant-column rules below come from those sections — never
assume a stack. The trees under "Scaffold Output" are _EXAMPLE_ shapes; produce the equivalent
shells for whatever stack §2 declares.
When to Use
- Starting a new backend module/package from scratch
- Starting a new frontend page/route/section from scratch
- Bootstrapping a new shared package
- Setting up a new background worker/processor
Start
python3 .cursor/context/context-builder.py \
--phase scaffold \
--task "$TASK" \
--agent scaffold-agent \
--keywords "module,service,controller,dto,entity,scaffold,migration"
Obey Context Packet tiers. Legacy: --use-legacy-loader.
Input Required
- User story path OR requirement description
- Target layer (from
AGENTS.md §3— e.g.api|web|worker|package) - Module name (e.g.,
billing,knowledge)
Scaffold Output
Mirror the real layout in AGENTS.md §3. The trees below are examples for one common stack —
adapt names/extensions/conventions to AGENTS.md §2.
EXAMPLE (NestJS backend module
{name}— replace with your framework's structure):
<backend_path>/modules/{name}/
├── {name}.module.ts (empty module shell)
├── {name}.controller.ts (empty controller with TODO routes)
├── {name}.service.ts (empty service with TODO methods)
├── dto/
│ ├── create-{name}.dto.ts
│ └── update-{name}.dto.ts
├── entities/
│ └── {name}.entity.ts (entity stub; include tenant column if §4 requires it)
└── index.ts
<backend_path>/database/migrations/
└── {timestamp}-Create{Name}Table.ts (up + down stubs)
<backend_path>/modules/{name}/{name}.service.spec.ts (empty test file)
EXAMPLE (Next.js App Router page
{path}— replace with your framework's structure):
<web_path>/app/{path}/
├── page.tsx (server-rendered shell with metadata)
├── loading.tsx (skeleton component)
├── error.tsx (error boundary)
└── _components/ (local components dir)
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.
- 4d ago First seen · 117 lines · 68 tokens per session scan A 27b6e42c069e
scaffold-agent is an agent published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 18d ago), licensed MIT. It adds 68 tokens to every session and 1,177 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.