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 liqiongyu/lenny_skills_plus --skill building-team-culturegit clone --depth 1 https://github.com/liqiongyu/lenny_skills_plusWrote 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/liqiongyu/lenny_skills_plus/building-team-culture)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/building-team-culture"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/building-team-culture/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/liqiongyu/lenny_skills_plus/building-team-culture"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/building-team-culture.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.00019 | $0.02210 |
| Opus 5 | $0.00010 | $0.01105 |
| Sonnet 5 | $0.00004 | $0.00442 |
| Haiku 4.5 | $0.00002 | $0.00221 |
Grade A, and why
building-team-culture 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 12d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building Team Culture
Scope
Covers
- Diagnosing the current culture (strengths, gaps, “sacred cows”, and where psychological safety breaks)
- Articulating culture as an operating system (principles → behaviors → decision rules)
- Defining team norms (communication, meetings, decisions, feedback, conflict)
- Designing a lightweight rituals/cadence map that reinforces the culture
- Planning rollout + reinforcement (coaching model, hiring/onboarding hooks, measurement)
When to use
- “Create a culture code / values and behaviors for my team.”
- “Our team norms are unclear—write decision-making + communication norms.”
- “Psychological safety is low—propose concrete practices and rituals to fix it.”
- “We’re scaling fast—help us preserve what works and change what doesn’t.”
- “I’m a new leader—help me listen first and then evolve the culture.”
When NOT to use
- You need to design team meeting cadence, rituals, or operating systems (use
team-rituals— this skill defines culture principles and norms, not the specific meeting structure) - You need engineering-specific practices like code review norms, on-call culture, or incident response culture (use
engineering-culture) - You need a full org restructure, reporting lines, or span-of-control redesign (use
organizational-design) - You need to improve your 1:1 practice or manager-report relationship (use
running-effective-1-1s) - You need an HR/legal investigation, harassment response, or policy/compliance guidance (involve HR/legal)
- You need to design a full org restructure, comp bands, or performance management system
- You need to run user/customer research (use
conducting-user-interviews) or design a full survey instrument (usedesigning-surveys)
Inputs
Minimum required
- Team context: function, size, seniority mix, reporting line, stage (startup/scale/enterprise)
- Working model: remote/hybrid/in-office; time zones; any planned org changes
- Current symptoms with 2–5 examples (e.g., slow decisions, blame, low ownership, stagnation)
- Desired outcomes: what should be more true in 4–12 weeks?
- Constraints: timeline, leadership support, meeting/time budget, “non-negotiables”
- Existing artifacts (if any): values, handbook, onboarding, meeting cadences, principles
- Confidentiality constraints (avoid names/PII; use anonymized examples)
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- eval/eval_config.json 1.5 KB
- eval/SHOWCASE.md 5.3 KB
- eval/with_skill.md 37 KB
- eval/without_skill.md 16 KB
- README.md 1.2 KB
- references/CHECKLISTS.md 1.9 KB
- references/EXAMPLES.md 949 B
- references/INTAKE.md 1.8 KB
- references/RUBRIC.md 5.5 KB
- references/SOURCE_SUMMARY.md 1.6 KB
- references/TEMPLATES.md 2.9 KB
- references/WORKFLOW.md 4.8 KB
- skillpack.json 383 B
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.
- 12d ago First seen · 136 lines · 19 tokens per session scan A 375e3ecec4b3
building-team-culture is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 2,210 once invoked, about $0.0001 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
hourly-rate-time
A time-management method based on assigning a high personal value to each hour. It treats time as a limited resource and uses that value to decide which tasks to do, outsource, or skip.
screen-detox
A habit-change framework for reducing non-work screen use such as social media, short videos, games, and endless scrolling.
monkey-mind-meditation
A meditation and reflection guide for a busy or anxious mind. It treats recurring thoughts as something to observe and examine, while noting that acute serious mental-health problems need professional care.
happiness-skill
A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.
exec-weekly-agenda-generator
Synthesize the past week across meetings, chat, email, and calendar to generate a ranked list of 5-10 topics for the weekly leadership team meeting. Use when the user asks to prep for their leadership meeting, generate meeting topics, build the agenda, or says "prep me for Monday.".
meeting-follow-up-pipeline
Turn a completed meeting into a debrief, decisions, action items, ready-to-send follow-up drafts, and proposed writebacks. Use when the user asks to debrief a meeting, process their last meeting, review meeting follow-ups, or run the meeting follow-up pipeline.