agentmods.dev

status

status is a command for Claude Code from Redtropig/harness-anchor. It costs 36 tokens per session (445 once invoked), scanned A, original, MIT.

A read-only command that gives a snapshot of a project's current state. It reports the active feature, feature counts, Git changes, documentation index freshness, session handoff, and tool health.

In plain words
What is it for?
Use it to see what work is active, whether the project index is current, what has changed in Git, and whether the project is ready for a handoff.
Why use it?
It gathers common project checks in one place without changing files. If the main report script fails, it can provide a smaller manual snapshot and identify that limitation.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the harness-anchor plugin — 14 skills, 9 commands, 5 agents, 5 hooks shipped together

not rated 13repo 1mo ago A scan 36 tokens original MIT

Good fit Use it to see what work is active, whether the project index is current, what has changed in Git, and whether the project is ready for a handoff.

Compare 6 commands from other repositories ↓
View source ↗ Redtropig/harness-anchor
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add Redtropig/harness-anchor
Claude Code
/plugin install harness-anchor

Made for: Claude Code.

Or install harness-anchor, the plugin that ships this one along with the rest of its 14 skills, 9 commands, 5 agents, 5 hooks.

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 status

README.md
[![agentmods](https://agentmods.dev/badge/commands/redtropig/harness-anchor/status.svg)](https://agentmods.dev/commands/redtropig/harness-anchor/status)
Your own site
<a href="https://agentmods.dev/commands/redtropig/harness-anchor/status"><img src="https://agentmods.dev/badge/commands/redtropig/harness-anchor/status.svg" alt="Measured on agentmods" height="20"></a>
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 445 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.00036 $0.00445
Opus 5 $0.00018 $0.00222
Sonnet 5 $0.00007 $0.00089
Haiku 4.5 $0.00004 $0.00044

Measured 7d ago against content hash 5d3fca4f37df, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, 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 7d 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/status.md · 46 lines

What it actually says

/status

Read-only project status overview. The report body is produced by a script — scripts/status-report.sh is the single source of truth for its sections and formatting (all 7: Status header / Active feature / Feature counts / Git working tree / TOC freshness / Session handoff head / Harness health).

Steps

  1. Run the report script:

    bash ${CLAUDE_PLUGIN_ROOT}/scripts/status-report.sh --target "$(pwd)"

  2. Print its output verbatim. Do not reformat, reorder, or summarize — the sections are the contract (tests pin them).

  3. Append at most ONE suggestion line when the report warrants it:

    • Project not anchored… → suggest /anchor
    • a state-budget entry carries OVER → point at /session-end (archival)
    • TOC freshness is absent or stale → mention /index-project

    One line, only when applicable — the report already carries its facts.

If the script fails

Report the script's error output verbatim first. Because /status is read-only, you MAY then degrade to a minimal manual snapshot (head of feature_list.json, git status --porcelain) — say explicitly that this is the degraded path. This is the only thin-wrapper command with a manual fallback; the others (/anchor, /cpp-init, /session-end) write state and must not be hand-replayed.

Boundary with /session-end

  • /status is read-only. It never writes feature_list.json, progress.md, or session-handoff.md.
  • /session-end writes handoff + progress + offers commit. Use it at the end of a session.
  • Use /status anytime you want a quick "where am I?" snapshot.
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. 7d ago First seen · 46 lines · 36 tokens per session scan A 5d3fca4f37df

Subscribe to this mod's changes

status is a command published in the GitHub repository Redtropig/harness-anchor (13 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 445 once invoked, about $0.0002 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.

Claude CodeLLMProject managementclaude-pluginskillssubagent-driven-developmentsuperpowers
Related

Other commands, from other repositories

swarm-migrate

Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…

yonatangross/orchestkit · 103 tokens

devloop

A command that runs a repeating software-development workflow from a code change through a pull request and review.

lollipopkit/cc-plugins · 37 tokens

test-tdd

Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.

guanyang/open-agent-hub · 32 tokens

fire-execute-plan

Execute a single plan with segment-based routing, per-task atomic commits, and test enforcement.

ThierryN/fire-flow · 17 tokens

standup

Hızlı günlük toplantı - dün, bugün, engeller - git ve görevlerden.

komunite/kalfa · 18 tokens

t00-status

A status-report command for a T00 task workspace, using files that record communication, tasks, and the previous session's next steps.

maysunAI/T00-zh · 28 tokens