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 anton-abyzov/vskill --skill project-wakegit clone --depth 1 https://github.com/anton-abyzov/vskillWrote 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/anton-abyzov/vskill/project-wake)<a href="https://agentmods.dev/skills/anton-abyzov/vskill/project-wake"><img src="https://agentmods.dev/badge/skills/anton-abyzov/vskill/project-wake/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/anton-abyzov/vskill/project-wake"><img src="https://agentmods.dev/badge/skills/anton-abyzov/vskill/project-wake.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.00126 | $0.01745 |
| Opus 5.5 | $0.00050 | $0.00698 |
| Sonnet 5.5 | $0.00025 | $0.00349 |
| Haiku 4.5 | $0.00013 | $0.00175 |
Grade A, and why
project-wake 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 today.
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
project-wake
One manual sweep of the current project. The user invoking $project-wake (or /project-wake) authorizes continuing interrupted work inside the rules below and nothing else. The coordinator routes, it does not implement: every action is one message to the thread that already owns the work.
1. Inventory
studio_thread_listwith nomachine(federated),includeArchived: false,limit: 100; repeat withcursor = nextCursoruntil it is null. Keeppartialand every unavailable or unauthorized member: their threads are unknown, never dead, and are never resumed or duplicated from here, except through step 4's handoff tools whenstudio_handoff_ready_listlists them.- Skip the calling thread, and threads whose
settledis true unless the user named them. - Remember each thread's machine. Pass that
machineon everystudio_thread_readandstudio_thread_sendfor a thread that is not on this machine.studio_queue_list,studio_queue_resume,studio_thread_configurationandstudio_pending_request_listonly see this machine: for a remote thread whose state depends on them, classify it unclear. - Call
studio_machine_listonce for which machines are ready. Provider quota is not listed anywhere: treat a provider as out of quota only when the thread's own failure text or a reset time says so.
2. Classify each thread
Read the latest run with studio_thread_read (view: "activity", runLimit: 1), paging with afterPosition = nextPosition until nextPosition is null. Use run status and the interrupt, failure and approval items, not the title.
| State | Evidence | Action |
|---|---|---|
| Running or queued | status running/starting/queued, or studio_queue_list shows undelivered messages that are not held |
Leave alone. Never add a second executor or watcher. |
| Already continued by the app | a newer run or a "Continue where you left off" / update-continuation message after the interrupt | Leave alone. |
| Cut off by update or restart | interrupted with cause service_update or restart; "Closed to install the SpecWithCode update."; failed with "The provider event stream closed unexpectedly" only when the same thread's activity also shows an update or restart notice; or cancelled with no interrupt request and an update or restart notice in the same thread |
Step 3, after the wait below. |
| Never started | "The provider did not start this turn within 2 minutes" or "Run interrupted before provider start" | Step 3, once. The app never retries these. |
| Stopped by a person | an interrupt request from the user, Stop, or cancelled with an interrupt request |
Leave it. A person's Stop is final; list it. A cancelled run with neither an interrupt request nor an update or restart notice is unclear. |
| Waiting on a person | a pending question or approval in the activity, or a studio_pending_request_list entry |
Leave it; list what is asked. |
| Usage limit | quota or rate-limit failure text, a reset time | Step 4. |
| Real failure | provider, tool or code error unrelated to an update | Do not retry. Report the error text and the owner. |
| Finished, not closed | completed run that says the work is done, with an increment that still has open tasks, unverified ACs or an open PR | Step 5. |
| Finished and closed | completed, increment closed or no remaining work | Nothing. Never wake it to poll. |
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.
- today Changed · +6 tokens per session 9eb2bd06e736
- yesterday First seen · 75 lines · 120 tokens per session scan A 0583a6c94911
project-wake is a skill published in the GitHub repository anton-abyzov/vskill (48 stars, last pushed today), licensed MIT. It adds 126 tokens to every session and 1,745 once invoked, about $0.0005 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-10-27.
Other skills, from other repositories
start-coding-task
Start a CodeAgent coding task from the user's request on one of their existing sessions, and report the session id so they can follow it.
supervise-session
Monitor, redirect, answer or stop an existing CodeAgent session.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
prismer-apple-reminders
Apple Reminders via remindctl: add, list, complete.
external-lib-flow
Workflow for onboarding an external private library so AI can use it without source access.