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 UrRhb/agentflow --skill sdlc-healthgit clone --depth 1 https://github.com/UrRhb/agentflowWrote 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/urrhb/agentflow/sdlc-health)<a href="https://agentmods.dev/skills/urrhb/agentflow/sdlc-health"><img src="https://agentmods.dev/badge/skills/urrhb/agentflow/sdlc-health.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.00043 | $0.01885 |
| Opus 5 | $0.00022 | $0.00942 |
| Sonnet 5 | $0.00009 | $0.00377 |
| Haiku 4.5 | $0.00004 | $0.00188 |
Grade A, and why
sdlc-health 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 8d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc-health
Run a comprehensive health check on the AgentFlow pipeline. Report status for every subsystem and provide actionable fix instructions for any issues found.
Execution
Run all checks below in order. Collect results, then print the summary at the end.
Checks
1. Prerequisites
Verify each of these exists and is functional:
- Claude Code CLI -- run
claude --versionto confirm it is accessible - git -- run
git --version - gh (GitHub CLI) -- run
gh --version, thengh auth statusto confirm authentication - Node.js -- run
node --version - npm -- run
npm --version - Conventions file -- check
~/.claude/sdlc/conventions.mdexists - Skill files -- check
~/.claude/skills/contains:spec-to-asana.md,sdlc-worker.md,sdlc-orchestrate.md,sdlc-stop.md,sdlc-health.md,sdlc-demo.md - Prompt files -- check
~/.claude/sdlc/prompts/contains:decompose.md,research.md,build.md,review.md,test.md
For any missing file, report exactly which file is missing and suggest running ./setup.sh from the agentflow repo.
2. PM Tool Connectivity
Test the Asana MCP connection:
- MCP responding -- call the Asana MCP
get_metool. If it responds with user info, the connection is live. - Can list projects -- call
get_projectsand confirm at least one project is returned - Can read tasks -- pick any project, call
get_tasksfor it - Can post comments -- do NOT actually post a comment; just confirm the
add_commenttool is available in the MCP toolset
If MCP is not responding, report: "Asana MCP server not connected. Check your MCP configuration in Claude Code settings."
3. Pipeline Status
Search for projects with [SDLC] in the name. For each one found:
- Count tasks per stage: Backlog, Research, Build, Review, Test, Integrate, Done, Needs Human
- List active workers: which slots (T2-T5) have assigned tasks, and which tasks
- Find the Status task (pinned task with
[LAST_SWEEP:]in description)- Extract the last sweep timestamp
- Calculate time since last sweep
- Classify: HEALTHY (<20 min), WARNING (20-60 min), CRITICAL (>60 min)
- List any tasks in "Needs Human" (task name and code)
- Report total estimated cost across all active tasks (sum
[COST:~$N]values) - Check for active merge locks (
[MERGE_LOCK:]in Status task) - Check for active sweep locks (
[SWEEP:RUNNING]in Status task)
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.
- 8d ago First seen · 154 lines · 43 tokens per session scan A fcd096b61f2c
sdlc-health is a skill published in the GitHub repository UrRhb/agentflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 1,885 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.