Borrowing it
Nothing to install: this file belongs to haojing8312/WorkClaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/haojing8312/WorkClaw/main/.agents/skills/workclaw-implementation-strategy/SKILL.mdgit clone --depth 1 https://github.com/haojing8312/WorkClawWrote 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/haojing8312/workclaw/workclaw-implementation-strategy)<a href="https://agentmods.dev/skills/haojing8312/workclaw/workclaw-implementation-strategy"><img src="https://agentmods.dev/badge/skills/haojing8312/workclaw/workclaw-implementation-strategy/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/haojing8312/workclaw/workclaw-implementation-strategy"><img src="https://agentmods.dev/badge/skills/haojing8312/workclaw/workclaw-implementation-strategy.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.00038 | $0.00472 |
| Opus 5.5 | $0.00015 | $0.00189 |
| Sonnet 5.5 | $0.00008 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
workclaw-implementation-strategy 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 1mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WorkClaw Implementation Strategy
Overview
Use this skill to front-load architecture and compatibility thinking before changing risky parts of WorkClaw. The goal is to choose the smallest safe implementation path before code changes begin.
When to Use
- Runtime behavior or chat orchestration changes
- Provider catalog, model routing, or integration changes
- Tool permission or approval-flow changes
- Sidecar bridge, browser automation, or protocol changes
- Vendor sync or upstream lane boundary changes
- IM, employee, or cross-surface routing changes
Do not use this for isolated copy edits or low-risk docs-only changes.
Inspect First
apps/runtime/src/apps/runtime/src-tauri/src/apps/runtime/sidecar/src/packages/*/src/- Related tests in
apps/runtime/src/__tests__/,apps/runtime/src-tauri/tests/,apps/runtime/sidecar/test/, andpackages/*/tests/
Required Output
- Changed surface area and affected modules
- Compatibility or rollout risks
- Recommended smallest safe implementation path
- Follow-on verification commands that will be required
- Release impact if the change touches packaging, vendors, or externally visible behavior
Output Template
Use this shape:
## Strategy Summary
- Change surface:
- Affected modules:
- Main risk:
- Recommended smallest safe path:
- Required verification:
- Release impact:
Core Pattern
- Identify the user-visible behavior or boundary being changed.
- Trace which frontend, Tauri, sidecar, and Rust modules participate.
- Prefer the narrowest change that preserves existing contracts.
- Call out uncertainty before editing instead of guessing.
- End with the verification and release-readiness follow-ups the change will require.
Common Mistakes
- Treating sidecar, Tauri, and frontend changes as isolated when the feature crosses all three.
- Editing provider or routing behavior without checking test coverage in the adjacent layers.
- Assuming vendor sync changes are mechanical when they may alter release expectations or upstream compatibility.
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.
- 1mo ago First seen · 59 lines · 38 tokens per session scan A d73c77b49a1a
workclaw-implementation-strategy is a skill published in the GitHub repository haojing8312/WorkClaw (141 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 472 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…