bearings

A fleet-status digest that summarizes current work so someone can continue after a break. The fleet is the project’s tracked set of tasks and workers.

In plain words
What is it for?
Use it for a bearings report, morning brief, catch-up, or “where did I leave off?” summary, with optional file or interactive-board output when explicitly requested.
Why use it?
It reduces the time needed to reconstruct what was happening and what remains open. By default it reports status without changing task or backlog state.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/kunchenguid/firstmate/bearings
Any agent
npx skills add kunchenguid/firstmate --skill bearings
Clone the repo
git clone --depth 1 https://github.com/kunchenguid/firstmate

Made for: Claude Code, Codex.

Per session 151 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,115 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00151 $0.04115
Opus 5 $0.00076 $0.02057
Sonnet 5 $0.00030 $0.00823
Haiku 4.5 $0.00015 $0.00411

Measured yesterday against content hash 519cb5eb647b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bearings 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 yesterday.

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.

.agents/skills/bearings/SKILL.md · 162 lines

How it starts

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

bearings

Generate a complete current snapshot from the fleet's current state, so the captain can resume in one read after a break, a night, or a context reset. Plain /bearings returns only the concise four-section chat digest. Only /bearings file writes the dated markdown report artifact and then returns the concise four-section chat digest linked to that report. Only /bearings lavish builds the interactive fleet board beside that digest, through bin/fm-bearings-board.sh (its header owns every board mechanic and the fm-bearings-board.v1 payload contract). A digest/build invocation is operationally read-only apart from the cooldown-limited reconcile instruction and its state/<id>.reconcile-nudged record, plus the explicit per-mode artifacts: the dated report in file mode, and in lavish mode the board file plus the answer binding and source registration that bin/fm-bearings-board.sh build records through their own owners. During that invocation it never tears down a task, merges a PR, dispatches new work, steers a worker except through that reconcile hook, answers a decision, cleans up work, or mutates backlog or task state beyond the reconcile record. Board answers are acted on later under the normal authority rules; this skill's board-wake section explicitly owns the guarded routing at that time.

Invocation modes

  • Plain /bearings gathers a fresh bounded snapshot and renders the four-section chat digest without creating, deleting, reading, or replacing data/status-report-<YYYY-MM-DD>.md.
  • /bearings file gathers a fresh bounded snapshot, replaces today's data/status-report-<YYYY-MM-DD>.md from scratch, and renders the four-section chat digest with a link or path to that report.
  • /bearings lavish gathers a fresh bounded snapshot, rebuilds and arms the interactive fleet board (the "Lavish board mode" section below), and renders the four-section chat digest with the board's URL inside it.
  • Treat file and lavish only as explicit invocation options in the slash command.
  • Do not treat natural-language requests such as "write a report", "save this", "persist it", "make a file", or "make a board" as file or lavish mode unless the invocation explicitly includes the standalone option.
  • When the captain asks to include PRs, pass the snapshot command's live-PR opt-in.
  • /bearings include PRs remains chat-only and makes the live-PR opt-in.
  • /bearings file include PRs and /bearings lavish include PRs compose the same way.

Read the full file on GitHub · 162 lines

Files

What ships with it

1 file 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.

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. yesterday First seen · 162 lines · 151 tokens per session scan A 519cb5eb647b

Subscribe to this mod's changes

bearings is a skill published in the GitHub repository kunchenguid/firstmate (4,420 stars, last pushed yesterday), licensed MIT. It adds 151 tokens to every session and 4,115 once invoked, about $0.0008 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.

Related

Other skills, from other repositories

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

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens