agentmods.dev

review-progress

A command that compares the local mcp-for-argo-workflows project with its Linear plan, a project task tracker. It checks issues, local files, tests, linting, implementation gaps, and blockers.

In plain words
What is it for?
Use it to review completed, active, ready, and blocked work, verify tests and linting, and produce a project progress report.
Why use it?
It reveals differences between planned work and the code that actually exists.

Command for Claude Code

5 2d ago A scan 0 tokens original Apache-2.0
View the source file pipekit/mcp-for-argo-workflows
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 commands/pipekit/mcp-for-argo-workflows/review-progress
Clone the repo
git clone --depth 1 https://github.com/pipekit/mcp-for-argo-workflows

Made for: Claude Code.

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 362 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.00000 $0.00362
Opus 5 $0.00000 $0.00181
Sonnet 5 $0.00000 $0.00072
Haiku 4.5 $0.00000 $0.00036

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

Security

Grade A, and why

review-progress 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 2d 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/review-progress.md · 59 lines

What it actually says

Review Project Progress

Review the current state of the mcp-for-argo-workflows project against the Linear plan.

Step 1: Gather Current State

  1. Fetch Linear issues using mcp__linear-server__list_issues with project: "mcp-for-argo-workflows"
  2. Check local codebase - What files exist? What's implemented?
  3. Run verification - Execute make lint and make test if Makefile exists

Step 2: Identify Discrepancies

Report on:

  1. Issues marked Done in Linear but not implemented locally
  2. Code implemented locally but issues still in Backlog
  3. Failing tests or lint errors
  4. Missing dependencies or blockers

Step 3: Generate Report

Produce a summary with:

## Progress Report: mcp-for-argo-workflows

### Overall Status
- Setup: X/10 complete
- MCP Tools: X/35 complete
- Testing: X/2 complete
- Documentation: X/3 complete

### Recently Completed
- [PIP-X] Issue title

### In Progress
- [PIP-X] Issue title - status notes

### Ready for Implementation
- [PIP-X] Issue title (dependencies met)

### Blocked
- [PIP-X] Issue title - blocked by [PIP-Y]

### Recommendations
1. Next priority task
2. Any issues needing attention

Step 4: Update Linear (Optional)

If discrepancies found, offer to:

  1. Update issue statuses to match reality
  2. Add progress comments to in-progress issues
  3. Flag any blockers or concerns

Begin by fetching the Linear project state.

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. 2d ago First seen · 59 lines · 0 tokens per session scan A f97d517c5582

Subscribe to this mod's changes

review-progress is a command published in the GitHub repository pipekit/mcp-for-argo-workflows (5 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 362 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.

Code reviewPlanningTesting
Related

Other commands, from other repositories

git

Git operations with intelligent commit messages and workflow optimization.

SuperClaude-Org/SuperClaude_Framework · 11 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

constitution

Create or update the project constitution from interactive or provided principle inputs.

github/spec-kit · 13 tokens