status

A status command for checking whether PACEflow is enabled, disabled, or inactive in the current project. PACEflow is the project system this command belongs to.

In plain words
What is it for?
Use it to inspect the current project's PACEflow status with the project's absolute path.
Why use it?
It reports the activation state and whether the current session is paused, helping explain what will happen next.

Command

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/paceaitian/paceflow/status
Clone the repo
git clone --depth 1 https://github.com/paceaitian/paceflow
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 147 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.00011 $0.00147
Opus 5 $0.00005 $0.00073
Sonnet 5 $0.00002 $0.00029
Haiku 4.5 $0.00001 $0.00015

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

Security

Grade A, and why

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

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.

plugin/commands/status.md · 14 lines

What it actually says

/paceflow:status

用户运行了 /paceflow:status。运行 Bash:node "${CLAUDE_PLUGIN_ROOT}/hooks/set-activation.js" --status --cwd "<当前项目 cwd 绝对路径>",把状态原样转述给用户(enabled / disabled / inactive、本 session 是否 paused,与对应下一步提示)。

规则

  • --cwd 必须传当前项目根的绝对路径(避免 shell cd 漂移读错 runtime)。
  • 把 helper 的 stdout 原样作为依据向用户报告,不要臆测状态。
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. yesterday First seen · 14 lines · 11 tokens per session scan A ef9845285995

Subscribe to this mod's changes

status is a command published in the GitHub repository paceaitian/paceflow (38 stars, last pushed 15d ago), licensed MIT. It adds 11 tokens to every session and 147 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.