AccessiWeather: Skill for Codex

.codex/skills/team/SKILL.md

team is a skill for Codex from Orinks/AccessiWeather. It costs 19 tokens per session (5,538 once invoked), scanned C, a copy of team, MIT.

A tmux-based way to run several Codex or Claude command-line workers in split terminal panes and coordinate them through shared files. tmux is a terminal tool that keeps multiple sessions running side by side.

In plain words
What is it for?
Use it to divide a large coding task among durable workers, dispatch work, track their state, and let execution continue beyond one short interaction.
Why use it?
It organizes long-running parallel work with shared task state, message passing, worktrees, and explicit worker controls. It is intended for the OMX command-line environment, not directly inside a normal Codex app session.

Skill for Codex

Written for Codex: installed under .codex/. Also seen: mentions subagents; mentions AGENTS.md; mentions Codex.

This is Orinks/AccessiWeather's own configuration. It tells Codex how to work on AccessiWeather itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything AccessiWeather configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Orinks/AccessiWeather. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Orinks/AccessiWeather/main/.codex/skills/team/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Orinks/AccessiWeather

Made for: Codex.

Wrote 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.

agentmods badge for team

README.md
[![agentmods](https://agentmods.dev/badge/skills/orinks/accessiweather/team/github.svg)](https://agentmods.dev/skills/orinks/accessiweather/team)
Your own site
<a href="https://agentmods.dev/skills/orinks/accessiweather/team"><img src="https://agentmods.dev/badge/skills/orinks/accessiweather/team/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.

agentmods 80×15 button for team

Your own site · 80×15
<a href="https://agentmods.dev/skills/orinks/accessiweather/team"><img src="https://agentmods.dev/badge/skills/orinks/accessiweather/team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,538 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.05538
Opus 5.5 $0.00008 $0.02215
Sonnet 5.5 $0.00004 $0.01108
Haiku 4.5 $0.00002 $0.00554

Measured 1mo ago against content hash 1147cf908ff2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

team scanned grade C 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 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

4. Confirm no external cleanup (`rm -rf .omx/state/team/<team>`) happened during execution
Origin

This is a copy

91% identical to team — 63 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.codex/skills/team/SKILL.md · 511 lines

How it starts

The opening of the file, as written. The whole thing — 511 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Team Skill

$team is the tmux-based parallel execution mode for OMX. It starts real worker Codex and/or Claude CLI sessions in split panes and coordinates them through .omx/state/team/... files plus CLI team interop (omx team api ...) and state files.

This skill is operationally sensitive. Treat it as an operator workflow, not a generic prompt pattern. In Codex App or plain outside-tmux sessions, do not present $team / omx team as directly available; launch OMX CLI from shell first, or stay on the nearest app-safe surface until the user explicitly wants the tmux runtime.

Team vs Native Subagents

  • Use Codex native subagents for bounded, in-session parallelism where one leader thread can fan out a few independent subtasks and wait for them directly.
  • Use omx team when you need durable tmux workers, shared task state, mailbox/dispatch coordination, worktrees, explicit lifecycle control, or long-running parallel execution that must survive beyond one local reasoning burst.
  • Native subagents can complement team/ralph execution, but they do not replace the tmux team runtime's stateful coordination contract.

What This Skill Must Do

GPT-5.5 Guidance Alignment

Use the shared workflow guidance pattern: outcome-first framing, concise visible updates for multi-step work, local overrides for the active workflow branch, validation proportional to risk, explicit stop rules, and automatic continuation for safe reversible steps. Ask only for material, destructive, credentialed, external-production, or preference-dependent branches.

When user triggers $team, the agent must:

  1. Invoke OMX runtime directly with omx team ...
  2. Avoid replacing the flow with in-process spawn_agent fanout
  3. Verify startup and surface concrete state/pane evidence
  4. If active team mode state is missing, initialize/sync it from canonical team runtime state before proceeding
  5. Keep team state alive until workers are terminal (unless explicit abort)
  6. Handle cleanup and stale-pane recovery when needed

Read the full file on GitHub · 511 lines

Changes

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.

  1. 1mo ago First seen · 511 lines · 19 tokens per session scan C 1147cf908ff2

Subscribe to this mod's changes

team is a skill published in the GitHub repository Orinks/AccessiWeather (24 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 5,538 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). It is 91% identical to team, differing in 63 lines, and is treated as a copy.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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…

microsoft/vscode · 72 tokens

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.

microsoft/vscode · 53 tokens

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.

microsoft/vscode · 53 tokens