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 ehrlich-b/wingthing --skill patternsgit clone --depth 1 https://github.com/ehrlich-b/wingthingWrote 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/ehrlich-b/wingthing/patterns)<a href="https://agentmods.dev/skills/ehrlich-b/wingthing/patterns"><img src="https://agentmods.dev/badge/skills/ehrlich-b/wingthing/patterns/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/ehrlich-b/wingthing/patterns"><img src="https://agentmods.dev/badge/skills/ehrlich-b/wingthing/patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.00612 |
| Opus 5.5 | $0.00011 | $0.00245 |
| Sonnet 5.5 | $0.00005 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
patterns 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.
What it actually says
Wingthing patterns
Choose the first supported route that satisfies the request:
- Local agent control with stdio MCP: let the current Claude or Codex session manage local sub-agents on existing code and provider logins. Read local sub-agents.
- Local sandboxed agent terminal for a person: run and later reattach to an agent on this computer. Read local sandbox.
- Direct remote MCP when machines differ: let one AI explicitly select and manage agents on several computers. Read remote orchestration.
- Self-hosted roost when a person needs a browser: for one person's remote machine, read personal remote wing. For a team browser host, read shared web roost. To connect an AI to that private roost, read shared roost agents.
- Optional entitled hosted relay: only when the account already has hosted-relay access and the selected wing allows it, read hosted browser wing.
Do not present planned features as patterns. In particular, Wingthing does not currently merge independent roosts into one inventory, provide browser-direct free terminals, prepare Git worktrees atomically, or expose remote schedules and delivery targets.
For every pattern, state these six placements before changing the host:
- Driver: human or LLM.
- Execution: the wing that owns the process.
- Workspace: the path and replica available on that wing.
- Display: terminal, browser terminal, or preview route.
- Credentials: the owner-scoped agent home or delegated credential.
- Memory: the durable project record and where it is replicated.
Current Wingthing routes execution. It does not synchronize a workspace or
durable memory between wings. A cwd must already exist on the selected wing.
Say this plainly when a pattern crosses machines.
Run wt doctor before changing a host. Use wt egg explain <agent> --json to
inspect the effective sandbox. Ask MCP clients to call
wingthing_capabilities before starting work.
Keep identities separate on shared hosts. The Wingthing login selects the egg owner. Claude, Codex, and other provider logins live in that owner's agent home. Never place provider tokens in MCP arguments, checked-in config, logs, or copied instructions. Preserve existing web-roost users while changing programmatic access unless the user has agreed to a migration.
What ships with it
8 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.
- embed.go 198 B
- hosted-browser-wing/INSTRUCTIONS.md 3.4 KB
- local-sandbox/INSTRUCTIONS.md 2.4 KB
- local-subagents/INSTRUCTIONS.md 3.0 KB
- personal-remote-wing/INSTRUCTIONS.md 6.6 KB
- remote-orchestration/INSTRUCTIONS.md 4.6 KB
- shared-roost-agents/INSTRUCTIONS.md 3.1 KB
- shared-web-roost/INSTRUCTIONS.md 4.0 KB
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 · 54 lines · 27 tokens per session scan A ff19617f2b03
patterns is a skill published in the GitHub repository ehrlich-b/wingthing (53 stars, last pushed 12d ago), licensed MIT. It adds 27 tokens to every session and 612 once invoked, about $0.0001 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.