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.
npx agentmods add skills/rlajous/claude-code-commands/statusnpx skills add rlajous/claude-code-commands --skill statusgit clone --depth 1 https://github.com/rlajous/claude-code-commandsWhat 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 | $0.00075 | $0.01184 |
| Opus 5 | $0.00037 | $0.00592 |
| Sonnet 5 | $0.00015 | $0.00237 |
| Haiku 4.5 | $0.00007 | $0.00118 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-runtime: follow runtime compatibility for invocation, delegation, configuration precedence, state paths, and permissions.
You are reporting the current position in the git-workflow pipeline and the recommended next step. This is read-only — never modify Git state, never create branches/commits/PRs. Follow each step in order.
Step 1: Parse Arguments
--html→ also generate a self-contained HTML status report (see Step 6).
Step 2: Load Context
Read the durable workflow context if present:
.git-workflow/pr-context.json— ticket id/title, branch, type, timestamps written by/start,/tdd,/commit..git-workflow/config.yaml—workflow.developmentBranch/productionBranch, issue tracker.
If a canonical file is absent, read its matching legacy .claude/ fallback as defined in the compatibility reference. If neither form exists, fall back to live Git/GitHub state only.
Step 3: Gather Live State (read-only)
git rev-parse --abbrev-ref HEAD # current branch
git status --porcelain # uncommitted changes?
git log --oneline origin/{devBranch}..HEAD # commits ahead of the dev branch
If gh is available and authenticated, also gather (skip gracefully on failure):
gh pr view --json number,title,state,reviewDecision,statusCheckRollup,url # PR for current branch, if any
gh release list --limit 1 # latest release
Step 4: Determine Pipeline Position
Infer which stage the work is in, in this order:
| Signal | Stage |
|---|---|
| On dev/prod branch, clean tree | Idle — no active feature |
| Feature branch, no commits ahead | Started — branch created, nothing committed |
| Feature branch, uncommitted changes | In progress — changes not yet committed |
| Commits ahead, no PR | Committed — ready to open a PR |
| PR open, checks pending/failing | In review (CI/{state}) |
PR open, CHANGES_REQUESTED |
In review — changes requested |
PR open, APPROVED |
Approved — ready to merge |
On a release/* branch |
Releasing |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 106 lines · 75 tokens per session scan A 5055fb7ad395
status is a skill published in the GitHub repository rlajous/claude-code-commands (30 stars, last pushed 4d ago), licensed MIT. It adds 75 tokens to every session and 1,184 once invoked, about $0.0004 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…