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 atman-33/workhub --skill team-onboardgit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/team-onboard)<a href="https://agentmods.dev/skills/atman-33/workhub/team-onboard"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/team-onboard/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/atman-33/workhub/team-onboard"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/team-onboard.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.00055 | $0.00383 |
| Opus 5.5 | $0.00022 | $0.00153 |
| Sonnet 5.5 | $0.00011 | $0.00077 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
team-onboard 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 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.
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.
What it actually says
Onboard a new team member
Produce a self-serve briefing so a newcomer can get productive from the shared folder alone.
Steps
- Resolve paths from
<team-context>; ask which project(s) the newcomer joins if not stated. - Read the sources (skim via indexes, don't dump whole files):
knowledge/_index.md→rules/and the most relevant topics_meta/conventions.md(IDs, branch naming, writing rules)- per project:
_index.md,prd/,docs/spec/spec.md,backlog/product-backlog.md, the latestreports/daily/*.html
- Write the briefing to
knowledge/onboarding/<date>-<name-or-role>.mdin the team content language:- What the team builds (from PRD/spec) and where things stand (from the latest report)
- The working cycle: backlog →
start-pbibranch convention → dev-main merge → daily report/spec update (link the design doc's cycle) - Reading list: the 5–10 most valuable existing notes, with paths
- First-week checklist (access to the shared folder, run
setup-team-context, etc.)
- Update
knowledge/onboarding/_index.md, append an activity-log line, and hand the user the briefing path.
Rules
- Link to existing notes instead of restating them — the briefing is a map, not a copy.
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.
- 1mo ago First seen · 36 lines · 55 tokens per session scan A c29bdc1d7760
team-onboard is a skill published in the GitHub repository atman-33/workhub (3 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 383 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
manifest-dev-help
Answer any question a person has about manifest-dev, with the why behind it: what it is for, its workflow and the autonomy ladder, each term a user meets (Manifest, Acceptance Criterion, Global Invariant, verification harness, recipe, ask-first, Lock, Debt, Ticket and the rest), how the parts relate, why each part…
academic-paper-workflow
Use when a user needs to plan, compose, or revise an academic paper in a staged workflow.
expo-launchpad-status
Show the current expo-launchpad pipeline state — phase, round, next role, pause reason — read-only.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
tasknotes
This skill should be used when the user asks to 'create a task', 'add a TODO', 'plan a sprint', 'organize tasks', 'track time', 'setup Kanban', 'create task from code', 'sync tasks with sprint', 'pomodoro session', 'start pomodoro', 'time estimate', or mentions TaskNotes, task management, or project planning in…
harness-onboarding
Use when generating a human-readable onboarding document from HARNESS.md, AGENTS.md, and REFLECTIONLOG.md — produces a friendly guide for new team members joining a harnessed project.