A project health-check procedure covering Git state, running services, the database, dependencies, tests, and development progress.

Use it to review a project's current branch and changes, service and database availability, dependency consistency, test results, issues, pull requests, and milestones.

It collects common project-status checks in one place, making it easier to spot broken services, unapplied database changes, dependency problems, or failing tests.

How xsovad06/sova configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to xsovad06/sova. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/xsovad06/sova/main/.claude/commands/status.md

Clone the repo

git clone --depth 1 https://github.com/xsovad06/sova

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/xsovad06/sova/status/github.svg)](https://agentmods.dev/commands/xsovad06/sova/status)

Your own site

<a href="https://agentmods.dev/commands/xsovad06/sova/status"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/xsovad06/sova/status"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 449 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.

Model	Per session	Once invoked
Fable 5.1	$0.00017	$0.00449
Opus 5.5	$0.00007	$0.00180
Sonnet 5.5	$0.00003	$0.00090
Haiku 4.5	$0.00002	$0.00045

Measured 16d ago against content hash a311267c5e31, 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 16d 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/status.md · 68 lines

What it actually says

Project Status Check

Perform a health check on the project and report current status.

Focus area: $ARGUMENTS

Checks

1. Git Status

Current branch and clean/dirty state
Uncommitted changes summary
Recent commits (last 5)
Any stale feature branches: git branch --merged main

2. Services

Check if project services are running (Docker, dev server, etc.)
Verify the application responds (health check endpoint if available)

3. Database

Check for unapplied migrations (see CLAUDE.md for the migration check command)
Verify database is accessible

4. Dependencies

Check for outdated or conflicting packages
Verify lock file is in sync with dependency manifest

5. Test Suite

Run the project's tests (see CLAUDE.md for commands)
Report pass/fail count and coverage if available

6. Project Progress

Read agent memory files if they exist (.claude/agent-memory/MEMORY.md)
Check open issues: gh issue list --assignee @me --state open --limit 10
Check open PRs: gh pr list --author @me --state open
Reference project milestones: gh issue list --state open --json milestone

7. Report

Provide a concise status dashboard:

Branch:       main (clean)
Services:     app [running] | db [running]
Migrations:   up to date
Tests:        120 passed, 0 failed
Open PRs:     2
Open Issues:  5
Next up:      <suggested focus>

Cross-References

Want to start working? Run /find-task or /standup
Need to run tests? Run /test

Rules

NEVER use emojis in any output

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.

16d ago Changed a311267c5e31
2mo ago First seen · 68 lines · 17 tokens per session scan A 5e7209262d13

Subscribe to this mod's changes

status is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 449 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-31.

Code review Git and workflow Testing ai-agents automation autonomous-development cli developer-tools meta

sova: Command for Claude Code