setup-team

setup-team is a cursor rule for Cursor from ahmadulhoq/agentskel. It costs 41 tokens per session (65 once invoked), scanned A, original, MIT.

A setup workflow for recording a project's team members, roles, ownership areas, and escalation contacts. It is used when the team roster has not been filled in yet.

In plain words
What is it for?
Use it to create the initial team roster in the project's shared memory.
Why use it?
It gives the agent a clear reference for who owns work and who should be contacted when problems need escalation.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to create the initial team roster in the project's shared memory.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/ahmadulhoq/agentskel/setup-team
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.

Clone the repo
git clone --depth 1 https://github.com/ahmadulhoq/agentskel

Made for: Cursor.

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

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

agentmods 80×15 button for setup-team

Your own site · 80×15
<a href="https://agentmods.dev/rules/ahmadulhoq/agentskel/setup-team"><img src="https://agentmods.dev/badge/rules/ahmadulhoq/agentskel/setup-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 65 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.00041 $0.00065
Opus 5.5 $0.00016 $0.00026
Sonnet 5.5 $0.00008 $0.00013
Haiku 4.5 $0.00004 $0.00006

Measured 1mo ago against content hash 1e5ef2f07943, 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 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.

.cursor/rules/setup-team.mdc · 7 lines

What it actually says

Read and follow the full workflow at .agents/workflows/setup-team.md.

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 First seen · 7 lines · 41 tokens per session scan A 1e5ef2f07943

Subscribe to this mod's changes

setup-team is a cursor rule published in the GitHub repository ahmadulhoq/agentskel (13 stars, last pushed 26d ago), licensed MIT. It adds 41 tokens to every session and 65 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.