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 engineering-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/engineering-culture)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/engineering-culture"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/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.
<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/engineering-culture"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/engineering-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.00022 | $0.02227 |
| Opus 5 | $0.00011 | $0.01113 |
| Sonnet 5 | $0.00004 | $0.00445 |
| Haiku 4.5 | $0.00002 | $0.00223 |
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 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Culture
Scope
Covers
- Diagnosing the current engineering culture and delivery system (technical, architectural, cultural, and management capabilities)
- Defining a clear engineering culture code (principles → behaviors → decision rules → anti-patterns)
- Aligning org structure with architecture (Conway’s Law) and reducing cross-team friction
- Increasing clock speed (safe shipping + experimentation throughput) and improving DevEx
- Creating a practical cross-functional workflow contract (how engineering + PM/Design/Marketing collaborate in the same toolchain)
- Making AI-assisted development safe and effective (humans as “architects”: spec, review, and oversight)
When to use
- “Help me improve engineering culture / DevEx and make it concrete.”
- “Our delivery is slow—build a plan to increase shipping speed without breaking things.”
- “Our org structure fights our architecture—analyze Conway’s Law and propose changes.”
- “We want tighter processes and faster experimentation (higher clock speed).”
- “Non-engineering functions struggle to work with engineering—define a shared workflow contract.”
- “We’re adopting AI coding tools/agents—set norms so engineers shift toward higher-level design and review.”
When NOT to use
- You need to respond to an active incident or outage (use incident response/runbooks)
- You need HR/legal policy, investigations, or employee relations handling (involve HR/legal)
- You only need to implement a specific technical improvement (e.g., “set up CI”) without culture/org/process work
- You need a full company strategy/roadmap prioritization across many bets (use
prioritizing-roadmap) - You want to build or refresh company-wide or team culture beyond engineering (use
building-team-culture) - You need to redesign org structure, reporting lines, or team topology at a company level (use
organizational-design) - You need a prioritized technical roadmap for specific projects or systems (use
technical-roadmaps) - You want to improve designer-engineer collaboration workflows specifically (use
design-engineering)
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.7 KB
- eval/SHOWCASE.md 4.9 KB
- eval/with_skill.md 44 KB
- eval/without_skill.md 14 KB
- README.md 1.8 KB
- references/CHECKLISTS.md 2.1 KB
- references/EXAMPLES.md 898 B
- references/INTAKE.md 3.1 KB
- references/RUBRIC.md 3.7 KB
- references/SOURCE_SUMMARY.md 1.5 KB
- references/TEMPLATES.md 4.3 KB
- references/WORKFLOW.md 3.9 KB
- skillpack.json 374 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 · 133 lines · 22 tokens per session scan A ce032650c10f
engineering-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 22 tokens to every session and 2,227 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
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.".
gws-workflow-email-to-task
Google Workflow: Convert a Gmail message into a Google Tasks entry.
gws-workflow-standup-report
Google Workflow: Today's meetings + open tasks as a standup summary.
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.