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/xsovad06/sova/statusgit clone --depth 1 https://github.com/xsovad06/sovaWhat 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.00017 | $0.00449 |
| Opus 5 | $0.00009 | $0.00225 |
| Sonnet 5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
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.
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-taskor/standup - Need to run tests? Run
/test
Rules
- NEVER use emojis in any output
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.
- yesterday First seen · 68 lines · 17 tokens per session scan A 5e7209262d13
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. 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.
Other commands, from other repositories
create-command
Create a new obsidian-second-brain command via interview - zero markdown editing required.
obsidian-architect
Scan a codebase and write a maintained set of architecture notes into the vault - overview, per-module notes, key decisions. Re-run to refresh without clobbering your edits.
obsidian-visualize
Generate a visual canvas map of your vault - see the shape of your second brain and how knowledge connects.
obsidian-export
Export a clean structured snapshot of the vault that any agent or tool can consume - flat JSON, markdown index, or an OKF (Open Knowledge Format) bundle.
obsidian-retrieval-eval
Measure how well vault search finds the right note for a natural-language question - recall@k and MRR, with the concrete failures.
obsidian-reindex
Refresh the vault's semantic search index and report coverage before and after.