A read-only dashboard for a specclaw project. It shows active changes, pending proposals, recently completed changes, progress, and overall project health.

Checking project status, viewing progress for a specific change, spotting unnumbered change folders, and seeing available update notices.

It gives the team one place to see what work is active, waiting, blocked, or finished.

status — Skill for Claude Code by chan4lk

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.

Any agent

npx skills add chan4lk/specclaw --skill status

Clone the repo

git clone --depth 1 https://github.com/chan4lk/specclaw

Made for: Claude Code.

Or install specclaw, the plugin that ships this one along with the rest of its 32 skills, 21 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/chan4lk/specclaw/status.svg)](https://agentmods.dev/skills/chan4lk/specclaw/status)

Your own site

<a href="https://agentmods.dev/skills/chan4lk/specclaw/status"><img src="https://agentmods.dev/badge/skills/chan4lk/specclaw/status.svg" alt="Measured on agentmods" height="20"></a>

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 453 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00037	$0.00453
Opus 5	$0.00018	$0.00227
Sonnet 5	$0.00007	$0.00091
Haiku 4.5	$0.00004	$0.00045

Measured 2d ago against content hash 69868bea6f97, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, 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.

plugins/specclaw/skills/status/SKILL.md · 21 lines

What it actually says

specclaw status

First, run specclaw-ensure-init .specclaw — idempotently creates .specclaw/ if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).

Show the project dashboard.

Refresh: specclaw-update-status .specclaw
Read .specclaw/STATUS.md and present:
- Active changes with progress %
- Pending proposals
- Recently archived changes
- Overall project health
- Unnumbered-folders hint: specclaw-update-status emits one extra line (to stdout, and italicised under the dashboard header) when change folders without a <NNN>- prefix exist — the count plus a pointer to /specclaw:renumber. Show it verbatim alongside the dashboard. It is a hint, not a prompt: do not ask whether to run the backfill, and expect nothing at all when the count is zero.
For a specific change, run specclaw-validate-change .specclaw <change> status to get a per-change snapshot.
If this project has a brownfield workstream (any .specclaw/analysis/, .specclaw/baseline/, or .specclaw/bootstrap/ artifact exists), point the user at /specclaw:bf-status after the dashboard. This dashboard covers the propose → plan → build → verify lifecycle only and says nothing about the bf-* phases; a rebuild's real state lives there.
Update check: run specclaw-check-update .specclaw. If it prints a line (a newer plugin version is published), show that line verbatim after the dashboard; if it prints nothing, say nothing. The script is fail-silent and gated by plugin.update_check in config.yaml — never treat its absence of output as an error.

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.

2d ago Changed · +1 lines 69868bea6f97
8d ago First seen · 20 lines · 37 tokens per session scan A 060123480b58

Subscribe to this mod's changes

status is a skill published in the GitHub repository chan4lk/specclaw (12 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 453 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-30.

Claude Code Project management agentic-workflow ai-agents anthropic claude spec-driven-development

raise-issue

Turns "this is broken" into a well-formed issue in the team's tracker, written in the codebase's own vocabulary. Built for someone who uses the product and does not read code — it asks a few plain-English questions, works out for itself which part of the code they are describing, checks whether the same thing has…

adamlinscott/claude-skills · 165 tokens

report-issue

Alias for the raise-issue skill. Turns "this is broken" into a well-formed issue in the team's tracker, written in the codebase's own vocabulary — a few plain-English questions, a check of which part of the code is being described, a duplicate check, then filing it once the person says yes. Built for someone who uses…

adamlinscott/claude-skills · 89 tokens

capture-lessons

Ship and capture lessons workflow. Creates the PR, updates lessons learned, updates documentation, generates the sprint retrospective, and updates the backlog. Use at the end of a sprint cycle, or when the user says "ship", "capture", "lessons", "retro", "retrospective", "wrap up", or "done with this sprint". Also use…

rbah31/claude-code-workflow · 100 tokens

sprint-plan

Sprint planning workflow. Creates a structured plan from the backlog with tasks, acceptance criteria, dependencies, and risks. Use when starting a new sprint, planning work, or when the user says "plan", "sprint", "what should we work on", or "next sprint". Always use this skill to start a sprint cycle — never plan…

rbah31/claude-code-workflow · 75 tokens

update-briefs

Updates the briefs/ shared memory directory after a sprint completes. Reads sprint outputs and writes structured summaries for other agents. Use after any sprint completes, or when the user says "update briefs", "sync state", "update project state", or "what changed". Also use automatically after /capture-lessons or…

rbah31/claude-code-workflow · 77 tokens

project-launch-checklist

Audits a project for hiring visibility before going public. Verifies README clarity for impatient hiring managers, checks evaluation setup, tests, CI/CD, config file, and deployment link. Generates a pre-launch audit report with gaps and priorities. Use when you're ready to make a project visible to hiring managers or…

AravindKurapati/claude-best-practices · 73 tokens