sdlc-demo

sdlc-demo is a skill for Claude Code, Codex from UrRhb/agentflow. It costs 33 tokens per session (2,240 once invoked), scanned A, original, MIT.

A five-minute demonstration of AgentFlow, a development pipeline that tracks work on an Asana board. It creates a small three-task project and completes one task in the current session.

In plain words
What is it for?
Trying AgentFlow in a Git repository with a package.json file, a connected Asana MCP server, and a separate Git branch.
Why use it?
It gives you a short, working example of the pipeline before you use it on a real project.

Skill for Claude CodeCodex

Part of the agentflow plugin — 6 skills, 4 agents, 1 MCP server shipped together

Install

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.

agentmods
npx agentmods add skills/urrhb/agentflow/sdlc-demo
Any agent
npx skills add UrRhb/agentflow --skill sdlc-demo
Clone the repo
git clone --depth 1 https://github.com/UrRhb/agentflow

Made for: Claude Code, Codex.

Or install agentflow, the plugin that ships this one along with the rest of its 6 skills, 4 agents, 1 MCP server.

Wrote 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.

agentmods badge for sdlc-demo

README.md
[![agentmods](https://agentmods.dev/badge/skills/urrhb/agentflow/sdlc-demo.svg)](https://agentmods.dev/skills/urrhb/agentflow/sdlc-demo)
Your own site
<a href="https://agentmods.dev/skills/urrhb/agentflow/sdlc-demo"><img src="https://agentmods.dev/badge/skills/urrhb/agentflow/sdlc-demo.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,240 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00033 $0.02240
Opus 5 $0.00016 $0.01120
Sonnet 5 $0.00007 $0.00448
Haiku 4.5 $0.00003 $0.00224

Measured 5d ago against content hash 99705dbbb1d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sdlc-demo 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.

plugin/skills/sdlc-demo/SKILL.md · 289 lines

How it starts

The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/sdlc-demo

Experience AgentFlow in 5 minutes. This command creates a minimal demo project, decomposes it into 3 tasks on your Asana board, and builds one task end-to-end -- all within the current session.

Prerequisites

Before running this demo, verify:

  1. Asana MCP connected -- run /sdlc-health to check. The demo needs to create an Asana project.
  2. Git repository -- you must be inside a git repo. Any project with a package.json works. If you do not have one, create a minimal project first:
    mkdir demo-project && cd demo-project
    git init && npm init -y
    
  3. Not on main branch -- create a demo branch:
    git checkout -b agentflow-demo
    

If any prerequisite is missing, stop and tell the user exactly what to fix before proceeding.

Process

Step 1: Create Demo Spec (30 seconds)

Create a temporary DEMO-SPEC.md in the current directory with this content:

# AgentFlow Demo Project

## Overview
A minimal hello-world project to demonstrate the AgentFlow pipeline.

## Tasks

### Task 1: Create greeting utility
Create `src/utils/hello.ts` that exports a `greet(name: string): string` function.
- Returns `"Hello, <name>! Welcome to AgentFlow."`
- Handle edge case: empty string returns `"Hello, World! Welcome to AgentFlow."`

### Task 2: Add unit tests (depends on Task 1)
Create `src/utils/__tests__/hello.test.ts` with test cases:
- greet("Alice") returns correct string
- greet("") returns default greeting
- greet with special characters works

### Task 3: Add npm script (depends on Task 1)
Add a `"greet"` script to `package.json` that runs: `npx ts-node -e "import {greet} from './src/utils/hello'; console.log(greet('Developer'))"`

Tell the user: "Created DEMO-SPEC.md with 3 tasks. Here is what will happen:"

  • Task 1: Create a utility function (this one will be built live)
  • Task 2: Write tests for it (would be built by Worker T3 in a full pipeline)
  • Task 3: Add an npm script (would be built by Worker T2 in a full pipeline)

Read the full file on GitHub · 289 lines

Changes

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.

  1. 5d ago First seen · 289 lines · 33 tokens per session scan A 99705dbbb1d0

Subscribe to this mod's changes

sdlc-demo is a skill published in the GitHub repository UrRhb/agentflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 2,240 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens