status

A project dashboard that reports the current state of the codebase, running agents, files, features, pending work, and local preview server.

In plain words
What is it for?
It helps check project details, agent progress, file changes, pending features, and whether the local development server is running.
Why use it?
It gathers scattered project information into one status report, making it easier to see what is finished, active, waiting, or broken.

Skill for Claude CodeCodex

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 skills/bugrabilge/bilge-development-kit/status
Any agent
npx skills add bugrabilge/bilge-development-kit --skill status
Clone the repo
git clone --depth 1 https://github.com/bugrabilge/bilge-development-kit

Made for: Claude Code, Codex.

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 466 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.00037 $0.00466
Opus 5 $0.00018 $0.00233
Sonnet 5 $0.00007 $0.00093
Haiku 4.5 $0.00004 $0.00047

Measured 2d ago against content hash 1592af414158, 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 2d 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/skills/status/SKILL.md · 101 lines

What it actually says

/status - Show Status

$ARGUMENTS


Task

Show current project and agent status.

What It Shows

  1. Project Info

    • Project name and path
    • Tech stack
    • Current features
  2. Agent Status Board

    • Which agents are running
    • Which tasks are completed
    • Pending work
  3. File Statistics

    • Files created count
    • Files modified count
  4. Preview Status

    • Is server running
    • URL
    • Health check

Example Output

=== Project Status ===

📁 Project: my-ecommerce
📂 Path: C:/projects/my-ecommerce
🏷️ Type: nextjs-ecommerce
📊 Status: active

🔧 Tech Stack:
   Framework: next.js
   Database: postgresql
   Auth: clerk
   Payment: stripe

✅ Features (5):
   • product-listing
   • cart
   • checkout
   • user-auth
   • order-history

⏳ Pending (2):
   • admin-panel
   • email-notifications

📄 Files: 73 created, 12 modified

=== Agent Status ===

✅ database-architect → Completed
✅ backend-specialist → Completed
🔄 frontend-specialist → Dashboard components (60%)
⏳ test-engineer → Waiting

=== Preview ===

🌐 URL: http://localhost:3000
💚 Health: OK

Auto-Collected Context

Before displaying status, gather live data using tools:

  1. Branch: Run git branch --show-current
  2. Last commit: Run git log --oneline -1
  3. Changed files: Run git status --short

Technical

Status uses these scripts:

  • python .agent/scripts/session_manager.py status
  • python .agent/scripts/auto_preview.py status
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. 2d ago First seen · 101 lines · 37 tokens per session scan A 1592af414158

Subscribe to this mod's changes

status is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 466 once invoked, about $0.0002 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.