status

status is a command for coding agents from rana/skills. It costs 0 tokens per session (347 once invoked), scanned A, original, MIT.

A project-status command that gives a short briefing on the current stage, recent changes, unfinished work, and next actions. It reads project notes and recent Git information, where Git records code changes and their history.

In plain words
What is it for?
Use it at the start of a coding session to understand where a project stands and what to do next.
Why use it?
It gathers status details that would otherwise require checking several files and commands manually. It also points out selected risks such as failing checks or large uncommitted changes.

Command

Part of the y plugin — 64 skills, 14 commands, 8 agents shipped together

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.

agentmods
npx agentmods add commands/rana/skills/status
Clone the repo
git clone --depth 1 https://github.com/rana/skills

Or install y, the plugin that ships this one along with the rest of its 64 skills, 14 commands, 8 agents.

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/rana/skills/status.svg)](https://agentmods.dev/commands/rana/skills/status)
Your own site
<a href="https://agentmods.dev/commands/rana/skills/status"><img src="https://agentmods.dev/badge/commands/rana/skills/status.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 347 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00347
Opus 5 $0.00000 $0.00173
Sonnet 5 $0.00000 $0.00069
Haiku 4.5 $0.00000 $0.00035

Measured 4d ago against content hash 0b3aead67694, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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 · 35 lines

What it actually says

Session orientation. Quick briefing on project state, recent changes, and next actions.

Read these in parallel:

  1. ROADMAP.md — find the section marked Current
  2. CONTEXT.md — find "Current State" and "Open Questions" (Tier 2 only)
  3. Run git log --oneline -8 for recent commits
  4. Run git status (never -uall) for working directory state
  5. Run git diff --stat HEAD~3..HEAD for recent change scope

Output

Deliver a dense briefing. No narrative filler.

Where We Are

  • Current stage name and one-sentence goal
  • Deliverables: N/M complete (list remaining by number — e.g., STG-006-1, STG-006-4, STG-006-9)

What Changed Recently

  • Last 3–5 commits (one line each, emphasize what shipped)
  • Uncommitted changes (if any — file count and nature)

What's Next

  • Next 1–2 unstarted deliverables from current stage (number + name)
  • Any Tier 2 open questions that could block near-term work

Active Concerns

  • Only if something looks off: failing CI, large uncommitted diffs, stale branches, schema drift

Keep the entire briefing under 200 words. If the project has no ROADMAP.md, fall back to README.md and recent git history.

$ARGUMENTS

If an argument is provided, focus the briefing on that area (e.g., "search", "ingestion", "frontend") — filter deliverables and recent commits to that domain.

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. 4d ago First seen · 35 lines · 0 tokens per session scan A 0b3aead67694

Subscribe to this mod's changes

status is a command published in the GitHub repository rana/skills (1 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 347 tokens. 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.