A project status dashboard that gathers task, session, verification, and Git information. Git is the system commonly used to track code changes and branches.

Reviewing task counts, finding the next actionable task, checking session state, viewing the current branch and recent commits, and running privacy and clean-worktree checks.

It gives developers one view of pending work, the current session, recent code changes, and checks that may be blocking progress.

status — Skill for Claude Code and Codex by andresharpe/dotbot

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 andresharpe/dotbot --skill status

Clone the repo

git clone --depth 1 https://github.com/andresharpe/dotbot

Made for: Claude Code, Codex.

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/andresharpe/dotbot/status/github.svg)](https://agentmods.dev/skills/andresharpe/dotbot/status)

Your own site

<a href="https://agentmods.dev/skills/andresharpe/dotbot/status"><img src="https://agentmods.dev/badge/skills/andresharpe/dotbot/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/andresharpe/dotbot/status"><img src="https://agentmods.dev/badge/skills/andresharpe/dotbot/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 633 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00024	$0.00633
Opus 5.5	$0.00010	$0.00253
Sonnet 5.5	$0.00005	$0.00127
Haiku 4.5	$0.00002	$0.00063

Measured 1mo ago against content hash 1621600786cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-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 1mo 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.

content/skills/status/SKILL.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Status Dashboard

Gather data from all available sources and present a structured status dashboard.

Data Collection

Collect the following in parallel where possible:

1. Task Queue (MCP tools)

Call task_list to get all tasks with their status, priority, and assignments
Call task_get_next to get the next actionable task
Compute counts by status: todo, analysing, analysed, in-progress, done, needs-input, skipped

2. Session State (MCP tool)

Call session_get_state to get current session info (if an active session exists)

3. Git Status (shell)

Run git status --short to check working tree cleanliness
Run git log --oneline -5 to show recent commits
Run git branch --show-current to identify the current branch

4. Verification Gates (shell)

Run pwsh .bot/hooks/verify/00-privacy-scan.ps1 — privacy/secrets scan
Run pwsh .bot/hooks/verify/01-git-clean.ps1 — working tree cleanliness

Presentation Format

Present results as a structured dashboard:

## Task Queue
| Status       | Count |
|--------------|-------|
| todo         | N     |
| analysed     | N     |
| in-progress  | N     |
| done         | N     |
| needs-input  | N     |

## Next Up
<Highest priority task in `todo` or `analysed` status — show ID, title, priority>

## Currently Active
<Any tasks in `analysing` or `in-progress` status — show ID, title, assignee>

## Blocked / Needs Input
<Tasks in `needs-input` status — show ID, title, reason>

## Session
<Active session info, or "No active session">

## Git Status
Branch: <branch>
Clean: <yes/no>
Recent commits:
  <last 5 commits>

## Verification
- Privacy scan: PASS/FAIL
- Git clean: PASS/FAIL

## Suggestions
<Actionable next steps based on the current state, e.g.:
 - "3 tasks are analysed and ready for implementation"
 - "1 task needs input — review task T-XXXXXXXX"
 - "Working tree has uncommitted changes — commit or stash before starting next task">

Rules

Read-only: Do not modify any state, tasks, or files
Show all statuses: Include zero-count rows so the full picture is visible
Be honest: If an MCP tool or hook fails, report the error rather than hiding it
Actionable suggestions: Always end with 1-3 concrete next steps based on what the data shows

Read the full file on GitHub · 81 lines

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.

1mo ago First seen · 81 lines · 24 tokens per session scan A 1621600786cd

Subscribe to this mod's changes

status is a skill published in the GitHub repository andresharpe/dotbot (52 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 633 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-30.

Git and workflow Project management ai-assisted-development ai-coding claude developer-tools gemini mcp-server

status

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Project Status Dashboard

Data Collection

1. Task Queue (MCP tools)

2. Session State (MCP tool)

3. Git Status (shell)

4. Verification Gates (shell)

Presentation Format

Rules

What this file has done since we first saw it

Other skills, from other repositories

papi-build

papi-auto

draft-issue

finish-task

run-task

close-task