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 nabeelhyatt/coworkpowers --skill workflow-workgit clone --depth 1 https://github.com/nabeelhyatt/coworkpowersWrote 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/nabeelhyatt/coworkpowers/workflow-work)<a href="https://agentmods.dev/skills/nabeelhyatt/coworkpowers/workflow-work"><img src="https://agentmods.dev/badge/skills/nabeelhyatt/coworkpowers/workflow-work.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.00063 | $0.01051 |
| Opus 5 | $0.00032 | $0.00526 |
| Sonnet 5 | $0.00013 | $0.00210 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
workflow-work 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 8d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work: Knowledge Work Execution Workflow
You are orchestrating the Work phase of the Compound Knowledge Work loop. Your job is to execute the plan systematically, producing high-quality output while staying adaptable.
The work itself should be straightforward if planning was thorough. If you find yourself struggling, the plan may need revisiting.
Process
Phase 1: Quick Start
- Read the plan completely. If a plan file exists, read it. If the plan was discussed in conversation, review it.
- Create a task list from the plan's steps using TaskCreate.
- Identify the right agent mindset for each step:
| Work Type | Primary Agent |
|---|---|
| Writing communications | executive-writer |
| Data analysis | analyst |
| Structuring decisions | decision-architect |
| Meeting preparation | meeting-orchestrator |
| Coaching conversation | coach |
| Task execution | task-executor |
- Check prerequisites. Does any step need user input before you can proceed?
Phase 2: Execute
Work through each step in order. For each step:
- Mark the task as in-progress.
- Apply the right agent mindset for the work type.
- Use the context from planning. Don't re-research what was already gathered.
- Validate as you go:
- Does this align with the stated goals?
- Does this account for the stakeholder considerations?
- Does this respect the constraints identified?
- Would the user be surprised by anything here?
- Flag blockers immediately. If you need user input, ask. Don't guess on important details.
- Mark the task as complete when done.
Phase 3: Quality Check
Before presenting output to the user:
- Self-review against success criteria from the plan.
- Run the review agents specified in the plan (see Review workflow).
- Check for completeness - did you address everything in the plan?
Phase 4: Present Output
Present the completed work to the user with:
- The deliverable itself (email draft, analysis, decision memo, etc.)
- Key decisions you made during execution and why
- Anything that deviated from the plan and why
- Suggested next steps or review areas
- Ask if they want to run the Review workflow for comprehensive quality assurance
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.
- 8d ago First seen · 136 lines · 63 tokens per session scan A 435b66cf834e
workflow-work is a skill published in the GitHub repository nabeelhyatt/coworkpowers (114 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 1,051 once invoked, about $0.0003 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.