CLAUDE

CLAUDE is a command for Claude Code from MarioEpkOne/PipelineIQ. It costs 0 tokens per session (547 once invoked), scanned A, original, MIT.

A directory-scoped set of Claude Code commands and reference files for planning, implementing, auditing, fixing, and reviewing code changes. Directory-scoped means the context applies only within this folder.

In plain words
What is it for?
Running slash commands for specifications, implementation plans, implementation, audits, fixes, pipeline work, and reviewing learned project knowledge.
Why use it?
It gives the agent project-specific instructions for several development workflows without making those instructions apply to the whole project or every directory.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

Part of the pipelineiq plugin — 10 commands, 6 agents shipped together

Good fit Running slash commands for specifications, implementation plans, implementation, audits, fixes, pipeline work, and reviewing learned project knowledge.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/marioepkone/pipelineiq/claude
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.

Clone the repo
git clone --depth 1 https://github.com/MarioEpkOne/PipelineIQ

Made for: Claude Code.

Or install pipelineiq, the plugin that ships this one along with the rest of its 10 commands, 6 agents.

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 CLAUDE

README.md
[![agentmods](https://agentmods.dev/badge/commands/marioepkone/pipelineiq/claude/github.svg)](https://agentmods.dev/commands/marioepkone/pipelineiq/claude)
Your own site
<a href="https://agentmods.dev/commands/marioepkone/pipelineiq/claude"><img src="https://agentmods.dev/badge/commands/marioepkone/pipelineiq/claude/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 CLAUDE

Your own site · 80×15
<a href="https://agentmods.dev/commands/marioepkone/pipelineiq/claude"><img src="https://agentmods.dev/badge/commands/marioepkone/pipelineiq/claude.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 547 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.00547
Opus 5 $0.00000 $0.00273
Sonnet 5 $0.00000 $0.00109
Haiku 4.5 $0.00000 $0.00055

Measured 8d ago against content hash 2a2973dc81e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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

commands/CLAUDE.md · 22 lines

How it starts

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

commands/ — Context for Claude

(Scoped to this directory only. See root CLAUDE.md for project-wide context.)

Architecture

The top-level .md files in commands/ are Claude Code slash commands. They are not called by each other directly -- pipeline.md reads reference files from references/pipeline/ and fills [VARIABLES] to build subagent prompts at runtime. pipeline-team.md does the same with references/pipeline-team/. The standalone commands (spec.md, impl-plan.md, impl.md, audit-implementation.md, fix.md) serve double duty as both user-facing commands and subagent instruction sources -- named agents read their own command files at startup rather than receiving embedded content from the orchestrator. learnings-review.md and spec-splitter.md are standalone user-facing commands that are not used as subagent instruction sources.

Invariants

  1. Line count matters. Several specs and audits have enforced line-count targets on pipeline.md and pipeline-team.md. Edits that add content may trigger audit failures in downstream pipeline runs if they push files past their targets. Check learnings.md for past instances of this.
  2. Reference files use bracket variables, not template literals. Placeholders like [WORKTREE_PATH], [SPEC_FILENAME], [MASTER_REPO_PATH], [COMMANDS_PATH] are filled by the orchestrator (pipeline.md) before passing to subagents. Using $VARIABLE or ${VARIABLE} syntax will not be substituted -- it will be passed literally to the subagent.
  3. phase6-merge.md checks for package.json before invoking patch-notes. If package.json doesn't exist at the project root (as is the case for this project currently), the patch-notes step is silently skipped.

Gotchas

  1. phase3-impl.md overrides impl.md's Phase 7 and Phase 8. The reference template tells the subagent to commit automatically (skip the user prompt) and skip the merge phase. An edit to impl.md Phase 7/8 behavior won't affect pipeline-driven runs -- only standalone /impl invocations.
  2. Re-audit appends to the existing audit file rather than creating a new one. The re-auditor agent reads its process from references/pipeline/re-audit-process.md and writes output into [AUDIT_FILENAME] as an addendum.

Read the full file on GitHub · 22 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. 8d ago First seen · 22 lines · 0 tokens per session scan A 2a2973dc81e7

Subscribe to this mod's changes

CLAUDE is a command published in the GitHub repository MarioEpkOne/PipelineIQ (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 547 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-31.