What is nobrainer-sessions?

A system for coordinating named, reusable sessions when work needs separate identities, write areas, handoffs, or parallel tasks.

Use it to set up project, research, or quality-assurance sessions, assign isolated tasks, recover interrupted work, and audit handoffs.

It makes multi-session work traceable and reduces confusion about who may edit what and whether a result was received correctly.

nobrainer-sessions — Skill for Claude Code by nobrainer-tech

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.

Any agent

npx skills add nobrainer-tech/nobrainer-tech-skills --skill nobrainer-sessions

Clone the repo

git clone --depth 1 https://github.com/nobrainer-tech/nobrainer-tech-skills

Made for: Claude Code.

Or install nobrainer-tech-skills, the plugin that ships this one along with the rest of its 15 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-sessions/github.svg)](https://agentmods.dev/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-sessions)

Your own site

<a href="https://agentmods.dev/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-sessions"><img src="https://agentmods.dev/badge/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-sessions/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-sessions"><img src="https://agentmods.dev/badge/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-sessions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,942 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00062	$0.01942
Opus 5	$0.00031	$0.00971
Sonnet 5	$0.00012	$0.00388
Haiku 4.5	$0.00006	$0.00194

Measured 6d ago against content hash 967cfb8e4ab1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

nobrainer-sessions 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 6d 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.

skills/nobrainer-sessions/SKILL.md · 176 lines

How it starts

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

NoBrainer Sessions

Operate visible sessions as a small control plane. Human-readable titles make the workflow understandable; exact identity and readback make it trustworthy. This skill does not invent the project plan, select the ready batch or replace implementation skills. nobrainer-dispatcher owns scheduling when a queue has multiple delegated units.

Describe the outcome, success criteria and verification, let one project-level session prepare bounded task prompts, and bring child results back for review. Exact identity, write ownership, stop gates and independent receive-audit are required; a convenient parent-child topology is not itself a safety contract.

For a single temporary native subagent, use its returned ID, scoped prompt, observable completion and artifact review; no durable registry or new visible task is required. Use this full protocol for durable or explicitly visible sessions.

Read references/protocol.md before setup, dispatch, or RECEIVE_AUDIT.

Choose the smallest topology

Default to one visible session named <repo> | MAIN. Add a session only when a measurable benefit outweighs coordination cost: isolated write scope, durable handoff, resume after interruption, independent parallel work, or reuse of a warm specialist.

Use stable role titles such as <repo> | QA or <repo> | RESEARCH when the responsibility persists. Use <repo> | <TASK_ID> for a bounded disposable work unit. Never treat a title as identity and never create a worker merely to make the topology look multi-agent.

Capability and identity gate

Discover the current harness capabilities for listing, creating, renaming, sending, reading, and waiting on visible sessions. Verify each mutation by readback. If exact session transport is unavailable, remain in MAIN and report the degraded mode; hidden workers are not equivalent to requested visible sessions.

Before reuse or dispatch, bind the target in the session registry:

THREAD_ID, HOST_ID, harness and current status;
repository, CHECKOUT or worktree, branch/base/HEAD;
role, task, write scope and isolation;
active-turn state and last successful readback.

Read the full file on GitHub · 176 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.

references/protocol.md 12 KB

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.

6d ago Changed · +25 lines 967cfb8e4ab1
7d ago Changed · +18 lines 511f0f32ea43
11d ago First seen · 133 lines · 62 tokens per session scan A 8b9a78ee5789

Subscribe to this mod's changes

nobrainer-sessions is a skill published in the GitHub repository nobrainer-tech/nobrainer-tech-skills (5 stars, last pushed 6d ago), licensed MIT. It adds 62 tokens to every session and 1,942 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-31.

Building agents Claude Code Multi-Agent Productivity agent-skills agentic-workflows codex cursor

next-action

Use when the user wants a next-action recommendation based on current state — reads handoff/git/lessons/STATE and proposes top-3 by impact. Trigger: '/next', 'what should I do next', 'next action'. Proposes only, never executes.

AlexZio00/sovereign-skills · 57 tokens

multi-agent-loop

Turn the current repository into a supervised multi-agent coding loop — spawn parallel AI coding agents in isolated git worktrees with file ownership, a shared radar, and human approval gates, then run the loop (status, standup, approvals) from one place.

anshulixyz/multi-agent-loop-kit · 55 tokens

nobrainer-sessions