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 agentmods add commands/asachs01/float-mcp/command-pipelinegit clone --depth 1 https://github.com/asachs01/float-mcpWhat 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 | $0.00000 | $0.00397 |
| Opus 5 | $0.00000 | $0.00198 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
command-pipeline 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.
This is a copy
100% identical to command-pipeline — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Execute a pipeline of commands based on a specification.
Arguments: $ARGUMENTS
Command Pipeline Execution
Parse pipeline specification from arguments. Supported formats:
Simple Pipeline
init → expand-all → sprint-plan
Conditional Pipeline
status → if:pending>10 → sprint-plan → else → next
Iterative Pipeline
for:pending-tasks → expand → complexity-check
Smart Pipeline Patterns
1. Project Setup Pipeline
init [prd] →
expand-all →
complexity-report →
sprint-plan →
show first-sprint
2. Daily Work Pipeline
standup →
if:in-progress → continue →
else → next → start
3. Task Completion Pipeline
complete [id] →
git-commit →
if:blocked-tasks-freed → show-freed →
next
4. Quality Check Pipeline
list in-progress →
for:each → check-idle-time →
if:idle>1day → prompt-update
Pipeline Features
Variables
- Store results:
status → $count=pending-count - Use in conditions:
if:$count>10 - Pass between commands:
expand $high-priority-tasks
Error Handling
- On failure:
try:complete → catch:show-blockers - Skip on error:
optional:test-run - Retry logic:
retry:3:commit
Parallel Execution
- Parallel branches:
[analyze | test | lint] - Join results:
parallel → join:report
Execution Flow
- Parse pipeline specification
- Validate command sequence
- Execute with state passing
- Handle conditions and loops
- Aggregate results
- Show summary
This enables complex workflows like:
parse-prd → expand-all → filter:complex>70 → assign:senior → sprint-plan:weighted
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.
- 2d ago First seen · 88 lines · 0 tokens per session scan A a8cb2c6c4d09
command-pipeline is a command published in the GitHub repository asachs01/float-mcp (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 397 tokens. A static security scan graded it A with 0 findings. It is 100% identical to command-pipeline, differing in 21 lines, and is treated as a copy.
Other commands, from other repositories
pm-init
Initialize local .pm governance; detect Spec Kit; if absent, analyze the repo and draft a PRD for user confirmation; after confirm/skip run a technical light scan.
pm-all
Full technical governance scan; rebuild .pm/dashboard. Default does not wait on draft PRD. Use --compare-baseline only after a confirmed PRD/charter.
pm-done
Close a todo (TODO-xxx), sync completed.md, refresh overview.
pm-export
Export desensitized governance summary markdown for sharing or machine switch.
pm-outline
Generate detailed project outline and draft charter from user intent (empty/new projects).
pm-status
Show governance health, wizard next step, all open blocking/high todos, and pending review count. Primary daily entry.