agentmods.dev

setup-team-context

setup-team-context is a skill for Claude Code from atman-33/workhub. It costs 67 tokens per session (591 once invoked), scanned A, original, MIT.

A setup tool for connecting a project to a shared team-operations folder. It creates the local team configuration and the shared folders used for knowledge, project planning, sprints, specifications, and reports.

In plain words
What is it for?
Use it when onboarding a machine, fixing a team-configuration problem, or adding a project. It can register the user, team folder, content language, and project structure.
Why use it?
It gives the machine and project a consistent place to find team information. It creates only missing files, so existing setup is not replaced.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the team-ops plugin — 13 skills shipped together

not rated 3repo changed 1mo ago A scan 67 tokens original MIT

Good fit Use it when onboarding a machine, fixing a team-configuration problem, or adding a project. It can register the user, team folder, content language, and project structure.

Compare 6 skills from other repositories ↓
View source ↗ atman-33/workhub
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add atman-33/workhub
Claude Code
/plugin install team-ops

Made for: Claude Code.

Or install team-ops, the plugin that ships this one along with the rest of its 13 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.

agentmods badge for setup-team-context

README.md
[![agentmods](https://agentmods.dev/badge/skills/atman-33/workhub/setup-team-context/github.svg)](https://agentmods.dev/skills/atman-33/workhub/setup-team-context)
Your own site
<a href="https://agentmods.dev/skills/atman-33/workhub/setup-team-context"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/setup-team-context/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.

agentmods 80×15 button for setup-team-context

Your own site · 80×15
<a href="https://agentmods.dev/skills/atman-33/workhub/setup-team-context"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/setup-team-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 591 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.00591
Opus 5.5 $0.00027 $0.00236
Sonnet 5.5 $0.00013 $0.00118
Haiku 4.5 $0.00007 $0.00059

Measured 1mo ago against content hash f1cfde5c39d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

setup-team-context 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.

plugins/team-ops/skills/setup-team-context/SKILL.md · 48 lines

How it starts

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

Set up the team-ops context

Configure this working directory to use a team-shared folder as the team's single source of truth (see ${CLAUDE_PLUGIN_ROOT}/docs/design.html).

Steps

  1. Collect inputs (ask only for what's missing):

    • teamRootPath — the locally synced shared folder (Google Drive / OneDrive / file server). The ai/ zone is created inside it.
    • me — the user's short name (used in activity-log entries).
    • Optionally a project name to scaffold, and the team content language (BCP 47 tag like ja / en; only applied when _meta/team.json does not exist yet).

  2. Run the setup script:

    node "${CLAUDE_PLUGIN_ROOT}/scripts/setup/init-team-context.mjs" \
  --team-root "<path>" --me "<name>" [--project "<name>"] [--language ja]

    It writes/merges .claude/team-context.json and keeps it out of git through .git/info/exclude — never .gitignore, which in a workhub vault is rewritten by every template update. If the output carries a warning that the file is already tracked, run the git rm --cached it names. It scaffolds ai/ (knowledge/, _meta/conventions.md, _meta/team.json, _meta/activity-log.md), and — with --project — the project skeleton (config/project.json, backlog/, sprints/, docs/spec/spec.md, reports/daily/). It only creates missing files, never overwrites.

  3. Configure the project's repos (when a project was scaffolded): open projects/<name>/config/project.json and replace the example entry with the real repositories — name, url, and each repo's devMainBranch (the project development main branch PBI work merges into).

  4. Report the JSON summary and remind the user that the new context is injected on the next session start.

Notes

  • The local config holds machine-local paths only; everything shared lives in the shared folder itself, so teammates just point at the same teamRootPath.
  • Changing the team language later = editing _meta/team.json.

Read the full file on GitHub · 48 lines

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. 1mo ago Changed · +3 lines f1cfde5c39d9
  2. 1mo ago First seen · 45 lines · 67 tokens per session scan A f9b5ae0a5875

Subscribe to this mod's changes

setup-team-context is a skill published in the GitHub repository atman-33/workhub (3 stars, last pushed 2d ago), licensed MIT. It adds 67 tokens to every session and 591 once invoked, about $0.0003 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.

Claude CodeProject managementclaude-code-plugincross-platformdesktop-appdeveloper-toolsobsidian
Related

Other skills, from other repositories

expo-launchpad-status

Show the current expo-launchpad pipeline state — phase, round, next role, pause reason — read-only.

SummerRiversound/expo-launchpad · 27 tokens

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…

parisgroup-ai/imersao-ia-setup · 106 tokens

issue-hygiene

How to write an issue somebody can act on, how to triage a pile of them, and the label vocabulary that stays useful. Use when filing, triaging, labelling, closing or linking issues.

Mikedev115/Aetox · 47 tokens

aetox-slice

Decomposes a technical specification or plan into vertical tracer-bullet tickets. Calculates directed dependency graphs (DAG), schedules prefactoring first, applies expand-contract sequencing for wide refactors, quizzes the user on ticket granularity, and emits atomic per-ticket files sized for optimal agent context…

Mikedev115/Aetox · 64 tokens

project-consolidation

Safely consolidate drifted/duplicate project folders in the memex vault — cwd-fragment folders (e.g. Apps-arena, GitHub-loom), duplicate/split projects (one project's content scattered across two folders), and name-mismatch folders. Trigger on "consolidate project folders", "merge duplicate projects", "fix project…

linxule/memex-plugin · 133 tokens

roadmap-update

Produit un document de roadmap dans output/ en croisant l'état actuel des epics beads avec les décisions et priorités documentées dans le wiki. Applique les règles anti-lissage — ne jamais compléter avec des connaissances d'entraînement, citer le wiki pour chaque affirmation de scope ou de priorité. Triggers — mettre…

evb87-tech/corpus · 94 tokens