Borrowing it
Nothing to install: this file belongs to Xsaven/vector-memory-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Xsaven/vector-memory-mcp/master/.claude/commands/task/status.mdgit clone --depth 1 https://github.com/Xsaven/vector-memory-mcpWrote 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.
[](https://agentmods.dev/commands/xsaven/vector-memory-mcp/status)<a href="https://agentmods.dev/commands/xsaven/vector-memory-mcp/status"><img src="https://agentmods.dev/badge/commands/xsaven/vector-memory-mcp/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.
<a href="https://agentmods.dev/commands/xsaven/vector-memory-mcp/status"><img src="https://agentmods.dev/badge/commands/xsaven/vector-memory-mcp/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00016 | $0.01322 |
| Opus 5.5 | $0.00006 | $0.00529 |
| Sonnet 5.5 | $0.00003 | $0.00264 |
| Haiku 4.5 | $0.00002 | $0.00132 |
Grade A, and why
task: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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Iron Rules
Always-summary (MEDIUM)
Always show summary at the end of output
- why: Provides quick overview regardless of query type
- on_violation: Append: "Summary: {total} total, {
completed}completed({pct}%)"
Input
STORE-AS($RAW_INPUT = $ARGUMENTS) STORE-AS($STATUS_QUERY = {query extracted from $RAW_INPUT})
Parse arguments
Parse captured input to detect query type
detect: STORE-AS($QUERY_TYPE = {detect: time|status|group|specific|default from $RAW_INPUT})- Time filters: yesterday, today, this week, this month, last 7 days, last N days
- Status filters:
completed,pending,in_progress,stopped - Grouping: by priority, by tags, by parent
- Specific: parent_id=N, task_id=N
- Empty: default overview statistics
Route query
Route to handler based on detected query type
route: IF(STORE-GET($RAW_INPUT) is empty) → Execute: default-stats workflow → ELSE → Execute: custom-query workflow based on STORE-GET($QUERY_TYPE) → END-IF
Default stats
Default overview when STORE-GET($RAW_INPUT) is empty
fetch: mcp__vector-task__task_stats('{}')store: STORE-AS($STATS = statistics response)format: Display: Total tasks: {total} → Display: Pending: {pending} | In Progress: {in_progress} | Completed: {completed} → Calculate: completion_pct = (completed/ total) * 100 → Render: [####------] {completion_pct}%
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.
- 2mo ago First seen · 95 lines · 16 tokens per session scan A 68538c112ccf
task:status is a command published in the GitHub repository Xsaven/vector-memory-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 16 tokens to every session and 1,322 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-09-01.
task:status compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| task:statusXsaven/vector-memory-mcp | Command | 0 | 8mo ago | MIT | A | 16 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |