design-team-norms

design-team-norms is a skill for Claude Code from jeffreytse/grimoire-core. It costs 52 tokens per session (2,055 once invoked), scanned A, original, MIT.

A guide for creating written team agreements about communication, decisions, conflict, and accountability.

In plain words
What is it for?
Use it when forming a team, after membership changes, or when people disagree about how work should be done.
Why use it?
It replaces unspoken assumptions with shared expectations, making recurring teamwork problems easier to address.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grimoire-business plugin — 145 skills shipped together

Good fit Use it when forming a team, after membership changes, or when people disagree about how work should be done.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/design-team-norms
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.

Any agent
npx skills add jeffreytse/grimoire-core --skill design-team-norms
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-business, the plugin that ships this one along with the rest of its 145 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 design-team-norms

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-team-norms/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/design-team-norms)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-team-norms"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-team-norms/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 design-team-norms

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-team-norms"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-team-norms.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,055 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.00052 $0.02055
Opus 5 $0.00026 $0.01027
Sonnet 5 $0.00010 $0.00411
Haiku 4.5 $0.00005 $0.00205

Measured 7d ago against content hash 98b917d4e129, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

design-team-norms 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 7d 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.

skills/business/leadership/skills/design-team-norms/SKILL.md · 147 lines

How it starts

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

Design Team Norms

Facilitate the co-creation of explicit written agreements that define how the team communicates, makes decisions, handles conflict, and holds each other accountable — so that expected behaviors are visible rather than assumed.

Why This Is Best Practice

Adopted by: Google Project Aristotle (2016) found that teams with explicitly established and consistently reinforced norms were the strongest predictor of team effectiveness above all other factors including individual skill; Lencioni's team clarity framework (used at thousands of organizations in his consulting practice) identifies behavior agreements as the foundation of functional teams; the US Army and Navy SEAL teams formalize "operating procedures" — the military equivalent of team norms — as foundational to unit cohesion under stress; Spotify's Squad model formalized working agreements as a required team artifact Impact: Google Project Aristotle (180 teams, 2+ years) found that norm clarity explained more variance in team performance than team composition, individual expertise, or management quality; Hackman's research ("Leading Teams," Harvard Business Review Press, 2002, 120 teams across multiple industries) found that explicit team norms reduced interpersonal conflict time by 30% and increased psychological safety by enabling "self-correction" — team members called each other out on norm violations rather than tolerating dysfunction; Lencioni estimates (from consulting work) that most team conflicts trace directly to implicit assumptions about behavior that were never made explicit Why best: Implicit norms are the assumption that "we all know how we should behave" — they are invisible until violated, unenforceable because they were never agreed upon, and enforced inconsistently because different team members have different implicit standards; explicit norms, co-created rather than dictated, produce three effects: they are more likely to be followed because the team agreed to them; they are enforceable when violated; and they surface implicit disagreements before they become conflicts

Read the full file on GitHub · 147 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. 7d ago First seen · 147 lines · 52 tokens per session scan A 98b917d4e129

Subscribe to this mod's changes

design-team-norms is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 22d ago), licensed MIT. It adds 52 tokens to every session and 2,055 once invoked, about $0.0003 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-09-03.

Related

Other skills, from other repositories

thomas-kilmann-conflict

Diagnoses and resolves conflicts using the Thomas-Kilmann five-mode framework: competing, collaborating, compromising, avoiding, and accommodating, mapped across assertiveness and cooperativeness dimensions. Use when navigating co-founder disagreements, mediating cross-functional team friction, choosing the right…

fatihguner/foreman · 84 tokens

org-report

Generate an executive organization brief (leadership chain, direct reports, extended teams, and vendor partners) for a target person. Produces a Word + PDF report from a directory MCP source (WorkIQ is the reference implementation) and displays it in a Copilot canvas. Triggers on "generate org report for X", "build…

fabioc-aloha/Alex_Skill_Mall · 89 tokens

coaching-techniques

GROW model, active listening, developmental feedback, and team growth approaches.

fabioc-aloha/Alex_Skill_Mall · 19 tokens

meeting-efficiency

Agenda design, time boxing, decision capture, async alternatives, and productive facilitation.

fabioc-aloha/Alex_Skill_Mall · 20 tokens

stakeholder-management

Influence mapping, communication strategies, and expectation management for complex organizations.

fabioc-aloha/Alex_Skill_Mall · 17 tokens

scaffolding-generator

Pattern-aware code scaffolding that detects existing conventions and generates new components matching the codebase style. Use when asked to "scaffold a component", "generate boilerplate", "create a new module", "bootstrap a service", "add a new endpoint", "create a new controller", or "add a new feature module".…

fabioc-aloha/Alex_Skill_Mall · 80 tokens