Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/TweekFawkes/promptsnpx agentmods add skills/tweekfawkes/prompts/doworkWrote 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/tweekfawkes/prompts/dowork)<a href="https://agentmods.dev/skills/tweekfawkes/prompts/dowork"><img src="https://agentmods.dev/badge/skills/tweekfawkes/prompts/dowork/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/tweekfawkes/prompts/dowork"><img src="https://agentmods.dev/badge/skills/tweekfawkes/prompts/dowork.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.00171 | $0.02479 |
| Opus 5 | $0.00086 | $0.01239 |
| Sonnet 5 | $0.00034 | $0.00496 |
| Haiku 4.5 | $0.00017 | $0.00248 |
Grade A, and why
dowork scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- For pure backend changes: exercise the new behavior through the API (`curl`, the project's API docs UI, or an integration test against the running stack). How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dowork — Run one backlog ticket end-to-end
You are completing exactly ONE backlog ticket from z_tickets/open/ and getting it ready to land. The user message that invoked this skill carries the ticket filename (no path) as the argument, for example add-password-reset.md. Treat that filename as $TICKET for the rest of this skill.
If the user message contains no filename, list z_tickets/open/*.md (excluding files whose names start with _ or .) and pick the first one in alphabetical order — the timestamp prefix makes that the oldest. If z_tickets/open/ has no matching files, print "no open tickets" and exit.
Authoritative paths
- Project root: the current working directory.
- Ticket source:
z_tickets/open/$TICKET - Ticket destination on success:
z_tickets/closed/$TICKET - Project conventions: read
CLAUDE.mdat the repo root (if present) and follow it. - Plan / lessons (optional, create if your CLAUDE.md mentions them):
tasks/todo.mdandtasks/lessons.md. - Stage deploy: whatever your project documents (commonly
bash scripts/deploy_stage.shor amake stagetarget). Used only for Tier 2 (step 6).
Operating principles (must follow)
- Smallest change that works. Land a thin vertical slice that satisfies the ticket. Do not opportunistically refactor.
- Follow existing patterns. Match the conventions you see in the surrounding code (framework choices, naming, file layout, lint rules). Do not introduce new dependencies unless the existing stack genuinely cannot solve the problem.
- Prove it works at the depth the change warrants (step 5). Never "looks right".
- One ticket per invocation. Don't pull adjacent fixes into this change — capture each one as its own backlog ticket with the
/newticketskill (see step 9) so it isn't lost. - Reversible by default. Prefer feature flags / config gates for risky behavior.
Required workflow
0. Seed this worktree (if your project uses one)
bash .claude/skills/gitready/scripts/seed-worktree.sh
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.
- 10d ago First seen · 152 lines · 171 tokens per session scan A ed22d275c0eb
dowork is a skill published in the GitHub repository TweekFawkes/prompts (2 stars, last pushed 1mo ago), licensed Unlicense. It adds 171 tokens to every session and 2,479 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.