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 b3rys/b3rys-team-os --skill b3os-team-member-lifecyclegit clone --depth 1 https://github.com/b3rys/b3rys-team-osWrote 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/b3rys/b3rys-team-os/b3os-team-member-lifecycle)<a href="https://agentmods.dev/skills/b3rys/b3rys-team-os/b3os-team-member-lifecycle"><img src="https://agentmods.dev/badge/skills/b3rys/b3rys-team-os/b3os-team-member-lifecycle/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/b3rys/b3rys-team-os/b3os-team-member-lifecycle"><img src="https://agentmods.dev/badge/skills/b3rys/b3rys-team-os/b3os-team-member-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 149 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 149 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00045 | $0.03423 |
| Opus 5 | $0.00023 | $0.01711 |
| Sonnet 5 | $0.00009 | $0.00685 |
| Haiku 4.5 | $0.00005 | $0.00342 |
Grade A, and why
b3os-team-member-lifecycle 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 11d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
b3rys Team Member Lifecycle
Use this skill for team-member onboarding(영입), offboarding(퇴사/비활성화), runtime migration(실행 환경 이전), and lifecycle dry-runs.
Onboarding(영입) — do NOT execute this file's checklist
The recruit flow is documented in full elsewhere, and that documentation is the current one. Go there first.
| What you need | Where |
|---|---|
| The recruit flow itself — dashboard wizard and API, OT stages, pairing | skills/b3os/references/recruit.md |
| Runtime prerequisites — install, auth, what preflight actually checks | skills/b3os/references/runtime-setup.md |
| A member that joined but won't answer | skills/b3os/references/troubleshooting.md |
Fastest path is the dashboard: Settings ▸ + 영입. One form takes id, name, role, runtime, mention aliases and persona together; the bot token and the rest are collected during provisioning.
For BYO runtimes (Hermes / OpenClaw) the runtime picker shows a setup link — follow it before recruiting. Preflight blocks activation until that runtime's auth exists, and finding that out mid-recruit wastes a cycle.
The numbered onboarding steps further down are a policy checklist, not a procedure: read them for the gates the recruit flow does not decide for you (owner routing, context visibility, approval boundaries).
Authoritative context — note which of these a fresh clone actually has:
| File | Present in a fresh clone? |
|---|---|
<repo>/rules/SHARED.md |
yes |
<repo>/rules/TEAM-OS.md |
no — render output, generated at startup from rules/TEAM-OS.template.md (src/server/lib/teamOsRender.ts). TEAM-OS.template.ko.md is a separate document with no runtime reader. Edit the template, never the output. |
<repo>/agents.json |
no — per-machine roster, deliberately untracked. loadRegistry returns [] until someone is recruited. |
Never tell a reader to open a file their clone does not have.
Authoritative context — note which of these a fresh clone actually has:
- Team rules:
<repo>/rules/TEAM-OS.template.md— this is the tracked source. The rendered<repo>/rules/TEAM-OS.mdis generated at server startup / on settings save and is not in a fresh clone (gitignored). Edit the template, never the output. - Shared state:
<repo>/rules/SHARED.md— tracked, present in a fresh clone. - Registry:
<repo>/agents.json— per-machine team roster, created when the first member is registered. Not in a fresh clone (gitignored);loadRegistryreturns[]when it is absent.
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.
- 11d ago First seen · 169 lines · 45 tokens per session scan A 3ff2f9f5351c
b3os-team-member-lifecycle is a skill published in the GitHub repository b3rys/b3rys-team-os (13 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 3,423 once invoked, about $0.0002 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.
Other skills, from other repositories
fable-commander
A planning and review workflow in which one model prepares decisions while selected models handle research and execution. It is written for Fable and Claude Code, tools for coordinating multi-step software work.
takt
A workflow engine that runs a task through a sequence of steps defined in a YAML file, using separate coding agents for the work.
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.
codebase-context-extractor
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.
skill-creator
Generates Anthropic Skills with complete workflow including GitHub PR creation and local download verification.
Research Synthesis Workflow
A step-by-step guide to synthesizing research from multiple sources into a coherent summary.