engineering-culture

engineering-culture is a skill for Claude Code, Codex from cnfeat/top-pm-skills. It costs 33 tokens per session (895 once invoked), scanned A, original, MIT.

Guidance for building a healthy engineering culture: the shared habits, team structure, and working practices that help developers do good work. It draws on practices from leaders of high-performing engineering teams.

In plain words
What is it for?
Use it to assess developer experience, improve technical practices, organize engineering teams, and support growth. It can help teams focus on speed, reliability, and developer satisfaction.
Why use it?
It helps identify whether development problems come from tools, team structure, skills, or process. It also helps choose an appropriate balance between standard rules and team independence.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to assess developer experience, improve technical practices, organize engineering teams, and support growth. It can help teams focus on speed, reliability, and developer satisfaction.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cnfeat/top-pm-skills/engineering-culture
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 cnfeat/top-pm-skills --skill engineering-culture
Clone the repo
git clone --depth 1 https://github.com/cnfeat/top-pm-skills

Made for: Claude Code, Codex.

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 engineering-culture

README.md
[![agentmods](https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/engineering-culture/github.svg)](https://agentmods.dev/skills/cnfeat/top-pm-skills/engineering-culture)
Your own site
<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/engineering-culture"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/engineering-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.

agentmods 80×15 button for engineering-culture

Your own site · 80×15
<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/engineering-culture"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/engineering-culture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 895 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.00033 $0.00895
Opus 5 $0.00016 $0.00447
Sonnet 5 $0.00007 $0.00179
Haiku 4.5 $0.00003 $0.00089

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

Security

Grade A, and why

engineering-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 11d 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.

参考skill/lenny-skills-main (2)/lenny-skills-main/skills/engineering-culture/SKILL.md · 71 lines

How it starts

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

Engineering Culture

Help the user build strong engineering culture using frameworks from 19 product leaders who have built high-performing engineering organizations.

How to Help

When the user asks for help with engineering culture:

  1. Diagnose the current state - Understand their team size, practices, and pain points
  2. Identify the bottleneck - Determine if the issue is DevEx, org structure, talent, or process
  3. Design for the right outcomes - Focus on speed, stability, and developer satisfaction
  4. Balance structure with autonomy - Help calibrate how much process is needed

Core Principles

DevOps is capabilities, not tools

Nicole Forsgren: "DevOps is not a toolchain you buy. Marketing teams labeled toolchains DevOps because they wanted your money. DevOps is a set of capabilities - technical capabilities, architectural capabilities, cultural capabilities, and lean management practices." Focus on integrated capabilities, not just implementing specific tools.

Conway's Law is powerful

Dhanji R. Prasanna: "Conway's Law can be really, really powerful. You ship your org structure. What you're organized as in terms of teams and collaborating groups matters a lot to what you build." Organizational structure directly dictates architecture and product quality.

Engineers are becoming architects

Scott Wu: "We've thought about Devin as really allowing engineers to go from bricklayer to architect. A lot of it is just getting to the point where you can do the high-level directing and specify things exactly how you want." The future of engineering involves shifting humans from manual coding to architectural oversight.

DevEx is the foundation

Nicole Forsgren: "Developer Experience is what it's like to build software, day to day. The friction they face, the workflows they have to go through. It's important because when DevEx is poor, everything else just isn't going to help." Flow state, cognitive load, and feedback loops are the three pillars.

Read the full file on GitHub · 71 lines

Files

What ships with it

1 file 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.

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. 11d ago First seen · 71 lines · 33 tokens per session scan A ceb38455f0ff

Subscribe to this mod's changes

engineering-culture is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 895 once invoked, about $0.0002 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.