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 nobrainer-tech/nobrainer-tech-skills --skill nobrainer-teamgit clone --depth 1 https://github.com/nobrainer-tech/nobrainer-tech-skillsWrote 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/nobrainer-tech/nobrainer-tech-skills/nobrainer-team)<a href="https://agentmods.dev/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-team"><img src="https://agentmods.dev/badge/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-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.
<a href="https://agentmods.dev/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-team"><img src="https://agentmods.dev/badge/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-team.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.00075 | $0.01285 |
| Opus 5 | $0.00037 | $0.00642 |
| Sonnet 5 | $0.00015 | $0.00257 |
| Haiku 4.5 | $0.00007 | $0.00128 |
Grade A, and why
nobrainer-team 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NoBrainer Team
Compose the smallest capable team for a concrete approved plan. This skill owns
capability selection and role design. nobrainer-dispatcher owns readiness,
batch ordering and backpressure after the plan is approved. nobrainer-sessions
owns actual visible session identity, transport, checkout isolation, leases and
receive-audit.
For a bounded native subagent, an inline assignment with exact returned ID, inputs, output, write scope, verifier and stop condition is enough. Keep it in the current plan; no visible task, persistent registry or queue is required. Read references/team-plan.md only for a durable team plan.
Start from work, not personas
Require an outcome, acceptance evidence and bounded work units. If they do not
exist, return to nobrainer-ultra or the approved specification. Do not invent a
team around vague titles such as architect, coder and tester.
Even an explicit Team invocation is a discovery trigger, not permission to skip Ultra's intake and planning boundary. Team may report the missing prerequisite and return control to Ultra, but it must not design roles from a vague goal.
For every work unit identify the method and capability actually needed. Inspect only metadata/frontmatter from installed skills first; load a full skill only after its trigger matches. Also inspect current project scripts, APIs, CLIs, tests and native client capabilities.
Build a compact local capability index from exact installed/project skill names, descriptions, source roots and collision status. Do not read every body or trust a title alone. This inventory replaces a permanent catalogue skill; refresh it only when sources change.
Choose the minimum roster
Default to <repo> | MAIN and no worker. Add a role only when it provides at
least one measurable benefit:
- an independent unit can shorten the critical path;
- a separate checkout or trust boundary prevents write conflict;
- a warm specialist will be reused across tasks;
- independent review materially reduces a stated risk;
- a handoff or resume boundary needs durable ownership.
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.
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 · +4 lines 85d7c9af1a75
- 7d ago Changed · +1 lines · -2 tokens per session cdf0a595f050
- 11d ago First seen · 124 lines · 77 tokens per session scan A 38cbda8dcdec
nobrainer-team is a skill published in the GitHub repository nobrainer-tech/nobrainer-tech-skills (5 stars, last pushed 6d ago), licensed MIT. It adds 75 tokens to every session and 1,285 once invoked, about $0.0004 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.
Other skills, from other repositories
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.
agent-communication-protocol
Open protocol for AI agent interoperability enabling standardized communication between agents, applications, and humans across different frameworks.
goal-lock
Agent Discipline Engine — lock the goal, run PLAN→DO→VERIFY→FINALIZE→OUTPUT loop, detect success masquerading. Triggers: '/goal-lock', '/goal-lock quick', 'goal lock', 'task harness'.
collab-audit
This skill should be used when the user types /collab-audit or requests AI collaboration diagnosis. Analyzes conversation history, artifacts, and work patterns to generate a 14-section AI Collaboration Audit. Behavioral analysis and feedback are bundled by design — separating them causes users to skip one, defeating…
code-autopsy
🔬 CODE AUTOPSY v7.2 "12 Questions + Quantified + Deployment Verdict + diff mode + CRITICAL hard cap + Factuality Gate".
doc-drift
Use this skill when the user wants to audit the memory and documents Claude Code loads into context — CLAUDE.md (user global + project + nested), MEMORY.md, @imports, .claude/skills, .claude/agents, .claude/commands, installed plugins — and detect four kinds of issues: outdated claims, mutually contradictory…