Claude-Pipeline: Command for Claude Code

.claude/commands/pipeline-scan.md

pipeline-scan is a command for Claude Code from TheAstrelo/Claude-Pipeline. It costs 0 tokens per session (1,222 once invoked), scanned A, original, MIT.

A command for scanning a codebase for likely problems, including missing tests, security issues, documentation gaps, code-quality concerns, outdated dependencies, and type-safety issues.

In plain words
What is it for?
Use it for a quick scan or request a deeper, security-only, test-only, dependency-only, or JSON-formatted report.
Why use it?
It surfaces several common maintenance risks in one review and ranks the findings by priority.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths.

This is TheAstrelo/Claude-Pipeline's own configuration. It tells Claude Code how to work on Claude-Pipeline itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Claude-Pipeline configures →

Reuse

Borrowing it

Nothing to install: this file belongs to TheAstrelo/Claude-Pipeline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/TheAstrelo/Claude-Pipeline/main/.claude/commands/pipeline-scan.md
Clone the repo
git clone --depth 1 https://github.com/TheAstrelo/Claude-Pipeline

Made for: Claude Code.

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 pipeline-scan

README.md
[![agentmods](https://agentmods.dev/badge/commands/theastrelo/claude-pipeline/pipeline-scan/github.svg)](https://agentmods.dev/commands/theastrelo/claude-pipeline/pipeline-scan)
Your own site
<a href="https://agentmods.dev/commands/theastrelo/claude-pipeline/pipeline-scan"><img src="https://agentmods.dev/badge/commands/theastrelo/claude-pipeline/pipeline-scan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for pipeline-scan

Your own site · 80×15
<a href="https://agentmods.dev/commands/theastrelo/claude-pipeline/pipeline-scan"><img src="https://agentmods.dev/badge/commands/theastrelo/claude-pipeline/pipeline-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,222 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.01222
Opus 5 $0.00000 $0.00611
Sonnet 5 $0.00000 $0.00244
Haiku 4.5 $0.00000 $0.00122

Measured 10d ago against content hash 570a16211019, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

pipeline-scan 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 10d 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.

.claude/commands/pipeline-scan.md · 195 lines

How it starts

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

Pipeline Scan Command

Proactive code analysis to detect issues and suggest improvements.

Arguments

  • $ARGUMENTS - Optional flags:
    • --full - Deep scan (slower, more thorough)
    • --security - Security-focused scan only
    • --tests - Test coverage scan only
    • --deps - Dependency scan only
    • --json - Output as JSON

Instructions

1. Quick Scan (Default)

Perform fast, non-blocking checks using the code-scanner agent:

Categories to check:

  1. Missing tests
  2. Security vulnerabilities
  3. Documentation gaps
  4. Code quality issues
  5. Outdated dependencies
  6. Type safety issues

2. Execute Scan

Load the code-scanner agent from .claude/agents/code-scanner.md.

Run checks based on flags:

  • Default: all categories
  • --security: security only
  • --tests: test coverage only
  • --deps: dependencies only

3. Aggregate Results

Collect all issues and rank by priority (Critical → Warning → Suggestion).

Priority order:

  1. Security critical (score: 100)
  2. Security moderate (score: 80)
  3. Missing tests for critical code (score: 70)
  4. Missing tests for new code (score: 50)
  5. Code quality issues (score: 45)
  6. Documentation gaps (score: 40)
  7. Outdated dependencies (score: 25)
  8. Type safety (score: 20)

4. Output Results

Default format:

/pipeline-scan

Found {N} opportunities:

  ⚠ {Category 1}
    └─ {Issue description}
    └─ Suggestion: /auto-pipeline "{suggested task}"

  ⚠ {Category 2}
    └─ {Issue description}
    └─ Suggestion: /auto-pipeline "{suggested task}"

  ⚠ {Category 3}
    └─ {Issue description}
    └─ Suggestion: /auto-pipeline "{suggested task}"

Quick stats:
  Files scanned: {count}
  TODOs found: {count}
  TypeScript coverage: {percent}%
  Last modified: {file} ({time} ago)

Run suggested pipelines? [1/2/3/all/none]

JSON format (--json):

{
  "issues": [
    {
      "category": "security",
      "priority": 80,
      "description": "npm audit found 2 moderate vulnerabilities",
      "suggestion": "fix npm audit vulnerabilities",
      "files": ["package.json"]
    }
  ],
  "stats": {
    "filesScanned": 47,
    "todosFound": 12,
    "typeScriptCoverage": 89,
    "lastModified": {
      "file": "src/api/payments.ts",
      "time": "2 hours ago"
    }
  }
}

Read the full file on GitHub · 195 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. 10d ago First seen · 195 lines · 0 tokens per session scan A 570a16211019

Subscribe to this mod's changes

pipeline-scan is a command published in the GitHub repository TheAstrelo/Claude-Pipeline (45 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,222 tokens. 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.