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.
git clone --depth 1 https://github.com/ai-sdlc-framework/ai-sdlcWrote 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/commands/ai-sdlc-framework/ai-sdlc/pipeline-status)<a href="https://agentmods.dev/commands/ai-sdlc-framework/ai-sdlc/pipeline-status"><img src="https://agentmods.dev/badge/commands/ai-sdlc-framework/ai-sdlc/pipeline-status.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.00019 | $0.00832 |
| Opus 5 | $0.00010 | $0.00416 |
| Sonnet 5 | $0.00004 | $0.00166 |
| Haiku 4.5 | $0.00002 | $0.00083 |
Grade A, and why
pipeline-status 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 7d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Show the current AI-SDLC pipeline status. Auto-detects the issue
tracker the same way the triage skill does — Backlog.md or GitHub.
Step 1 — Detect mode
- If
$ARGUMENTSis empty → branch mode (look up open PRs on the current branch) - If
$ARGUMENTSmatches^[A-Za-z][A-Za-z0-9]*-\d+$(e.g.AISDLC-42) → Backlog task mode - If
$ARGUMENTSis\d+or#\d+→ GitHub issue mode
Don't hardcode --repo. The cwd's git remote drives gh.
Step 2a — Branch mode (no argument)
BRANCH=$(git branch --show-current)
echo "Branch: $BRANCH"
PR_NUM=$(gh pr list --head "$BRANCH" --json number --jq '.[0].number // empty')
if [ -n "$PR_NUM" ]; then
gh pr view "$PR_NUM" --json number,title,state,statusCheckRollup,reviews
gh pr checks "$PR_NUM"
else
echo "No open PR on this branch."
fi
Step 2b — GitHub issue mode
gh issue view "$ARGUMENTS" --json number,title,state,labels,assignees
# Find linked PRs via "Closes #N" / "Fixes #N" backlinks
gh pr list --search "linked:$ARGUMENTS" --json number,title,state,headRefName,statusCheckRollup
Step 2c — Backlog task mode
Use mcp__backlog__task_view with id $ARGUMENTS. The task carries
title, status, labels, priority, assignee. Map status to a
pipeline stage:
| Backlog status | Pipeline stage |
|---|---|
Draft |
not yet ready (missing AC) |
To Do |
admitted, awaiting agent |
In Progress |
agent working |
Done (still in backlog/tasks/) |
closing — needs task_complete |
File in backlog/completed/ |
closed |
Then look for a PR that mentions the task id in its body or branch name:
gh pr list --search "$ARGUMENTS in:title,body" --json number,title,state,statusCheckRollup
Step 3 — Report
Present a clear status summary:
- Issue / task — title, state/status, labels (which pipeline stage)
- PR — number, state, CI checks (pass/fail/pending), review state
- Coverage — codecov status if available (
gh pr checksoutput already includes it) - Next action — what needs to happen next:
- CI failing → "run
/fix-pr <N>" - Reviews requesting changes → "run
/fix-pr <N>" or "address review findings" - All green → "ready for human merge"
- Backlog task in
Donebut file still inbacklog/tasks/→ "runmcp__plugin_ai-sdlc_ai-sdlc__task_completeto archive (drop-in replacement that preserves unknown frontmatter keys, AISDLC-73)"
- CI failing → "run
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.
- 7d ago First seen · 84 lines · 19 tokens per session scan A e7debe0fd656
pipeline-status is a command published in the GitHub repository ai-sdlc-framework/ai-sdlc (105 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 832 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-30.
Other commands, from other repositories
README
Custom commands are reusable prompt templates you invoke with /command-name in Claude Code.
lint-fix
Run all formatters and linters with auto-fix.
go-conventions
Scan the current Go repo and write .claude/go-conventions.md — a project-specific convention file that rules/go.md loads on every session instead of re-scanning the codebase from scratch. Use when starting work in a new Go repo, when conventions have drifted, or when --refresh is passed to merge in new patterns.
go-test
Enforce TDD workflow for Go. Write table-driven tests first, then implement. Verify 80%+ coverage with go test -cover.
go-build
Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.
go-review
Comprehensive Go code review for idiomatic patterns, concurrency safety, error handling, and security. Invokes the go-reviewer agent.