status

status is a command for Claude Code from repowise-dev/repowise. It costs 22 tokens per session (282 once invoked), scanned A, original, AGPL-3.0.

A command for checking the health of a Repowise search index, including its synchronization state, page counts, data provider, and token usage.

In plain words
What is it for?
Use it to inspect Repowise sync status, indexed page totals, provider details, and token consumption.
Why use it?
It makes the index's current state visible when searches may be out of date or resource usage is a concern.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the repowise plugin — 6 skills, 18 commands, 3 hooks, 1 MCP server shipped together

Good fit Use it to inspect Repowise sync status, indexed page totals, provider details, and token consumption.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/repowise-dev/repowise/status
About the project

Repowise is a codebase intelligence tool that indexes source code, dependencies, history, tests, documentation, and architectural decisions to answer questions about software projects. It helps developers and coding agents understand systems, assess change impact, identify dead or risky code, and improve code health. Its catalogue add-ons extend agent workflows for using Repowise.

repowise-dev/repowise · 7,792 stars · on GitHub · repowise.dev

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/repowise-dev/repowise

Made for: Claude Code.

Or install repowise, the plugin that ships this one along with the rest of its 6 skills, 18 commands, 3 hooks, 1 MCP server.

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/repowise-dev/repowise/status/github.svg)](https://agentmods.dev/commands/repowise-dev/repowise/status)
Your own site
<a href="https://agentmods.dev/commands/repowise-dev/repowise/status"><img src="https://agentmods.dev/badge/commands/repowise-dev/repowise/status/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 status

Your own site · 80×15
<a href="https://agentmods.dev/commands/repowise-dev/repowise/status"><img src="https://agentmods.dev/badge/commands/repowise-dev/repowise/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 282 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 unknown 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.00022 $0.00282
Opus 5.5 $0.00009 $0.00113
Sonnet 5.5 $0.00004 $0.00056
Haiku 4.5 $0.00002 $0.00028

Measured 11d ago against content hash 227bca1dbf3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-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 11d 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.

plugins/claude-code/commands/status.md · 25 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 11d ago Changed 227bca1dbf3f
  2. 1mo ago First seen · 25 lines · 22 tokens per session scan A f7f0b81b3759

Subscribe to this mod's changes

status is a command published in the GitHub repository repowise-dev/repowise (7,792 stars, last pushed today), licensed AGPL-3.0. It adds 22 tokens to every session and 282 once invoked, about $0.0001 per session on Opus 5.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.