davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.
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 skills add davepoon/buildwithclaude --skill work-statusgit clone --depth 1 https://github.com/davepoon/buildwithclaudeWrote 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/davepoon/buildwithclaude/work-status)<a href="https://agentmods.dev/skills/davepoon/buildwithclaude/work-status"><img src="https://agentmods.dev/badge/skills/davepoon/buildwithclaude/work-status.svg" alt="Measured on agentmods" 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.00046 | $0.00280 |
| Opus 5 | $0.00023 | $0.00140 |
| Sonnet 5 | $0.00009 | $0.00056 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
work-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 yesterday.
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
WORK Status
Check and report the current status of WORKs and TASKs.
How to Check
- Read
works/WORK-LIST.mdfor the master index of all WORKs - For a specific WORK, read
works/WORK-NN/PROGRESS.mdfor TASK-level progress - For a specific TASK, read
works/WORK-NN/TASK-NN_result.mdfor completion details
Status Values
| Status | Meaning |
|---|---|
IN_PROGRESS |
WORK created, TASKs being executed |
DONE |
All TASKs committed — committer auto-sets on last TASK |
COMPLETED |
Archived to _COMPLETED/ — set during push |
Display Format
WORK Status
WORK-01: User Authentication ✅ 5/5 completed
WORK-02: Payment Integration 🔄 2/4 in progress
WORK-03: Admin Dashboard ⬜ 0/6 pending
Arguments
Query: $ARGUMENTS
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.
- yesterday First seen · 36 lines · 46 tokens per session scan A d8f159a8c7e8
work-status is a skill published in the GitHub repository davepoon/buildwithclaude (3,419 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 280 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-09-05.
Other skills, from other repositories
01-sdlc
Autonomously orchestrates a request from framing to a draft pull request, isolating implementation, independent review, and final outcome challenge. Use when the user wants to deliver a change end to end. Not for running one development step.
08-three-amigos
Assesses an Epic or Story through one product, delivery, or quality lens, then reconciles three caller-supplied reports. Use when the user wants to refine one before a backlog change. Not for spawning or writing.
10-task
Produces or refines a backlog Task for bounded delivery work without independent user value. Use when the user wants to create, link, order, estimate, transition, or complete one. Not for User Stories, Spikes, Defects, or implementation.
01-ticket-info
Retrieve and display a ticket from the configured ticketing tool. Use when the user wants to see, show, or look up a ticket's details. Not for creating a ticket, or commenting on, transitioning, or reassigning one.
00-async-dev
Drive the async-dev pipeline from one entry point, whether setup, run, or review. Use when the user wants to install async dev, run a ready issue, or address PR review comments, or on a webhook trigger. Not for plain status checks.
11-explore
Explore the current project across its tooling, context, and codebase. Use to survey what is installed, see what is available, or find which skill, agent, or rule fits a goal. Not for choosing the next step or running an item; it only points.