Borrowing it
Nothing to install: this file belongs to bugrabilge/bilge-development-kit. 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/bugrabilge/bilge-development-kit/main/.claude/skills/status/SKILL.mdgit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWrote 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/skills/bugrabilge/bilge-development-kit/status)<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/status"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/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/skills/bugrabilge/bilge-development-kit/status"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/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.00037 | $0.00466 |
| Opus 5.5 | $0.00015 | $0.00186 |
| Sonnet 5.5 | $0.00007 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00047 |
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 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.
What it actually says
/status - Show Status
$ARGUMENTS
Task
Show current project and agent status.
What It Shows
-
Project Info
- Project name and path
- Tech stack
- Current features
-
Agent Status Board
- Which agents are running
- Which tasks are completed
- Pending work
-
File Statistics
- Files created count
- Files modified count
-
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:
- Branch: Run
git branch --show-current - Last commit: Run
git log --oneline -1 - Changed files: Run
git status --short
Technical
Status uses these scripts:
python .agent/scripts/session_manager.py statuspython .agent/scripts/auto_preview.py status
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 · 101 lines · 37 tokens per session scan A 1592af414158
status is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 466 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.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.