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 running-effective-1-1sgit 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/running-effective-1-1s)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/running-effective-1-1s"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/running-effective-1-1s/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/running-effective-1-1s"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/running-effective-1-1s.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.00040 | $0.02268 |
| Opus 5 | $0.00020 | $0.01134 |
| Sonnet 5 | $0.00008 | $0.00454 |
| Haiku 4.5 | $0.00004 | $0.00227 |
Grade A, and why
running-effective-1-1s 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 9d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running Effective 1:1s
Scope
Covers
- Designing a lightweight 1:1 operating system (purpose, cadence, meeting types, shared docs)
- Running 1:1s as coaching conversations (not just status updates)
- Holding career development conversations (life story → future dreams → action plan)
- Doing basic wellbeing/recovery check-ins (joy/energy) without crossing into therapy/medical advice
- Running skip-levels and special sessions (e.g., post-crisis “make them feel heard” 1:1s)
When to use
- “My 1:1s are turning into status updates—help me redesign them.”
- “Create a 1:1 agenda + shared doc template for me and my direct reports.”
- “I’m a new manager—set up my 1:1 cadence and question bank.”
- “Help me run better career conversations in 1:1s.”
- “Plan a skip-level program and templates.”
When NOT to use
- You need HR/legal guidance, an investigation, or a performance improvement plan (involve HR/legal; use your company process)
- You need a project status meeting cadence (use team/ops rituals; 1:1s should not be the primary status channel)
- The situation involves immediate safety/mental health crisis (seek professional help and follow company policy)
- You want to develop a PM's product skills through structured coaching (use
coaching-pms) - You need to design team-wide meetings, standups, or group rituals (use
running-effective-meetings) - You want to delegate work effectively and track outcomes (use
delegating-work) - You want to manage your relationship upward with your own boss (use
managing-up)
Inputs
Minimum required
- Your role and context (manager level, org type, function, time zones)
- Who the 1:1s are for (directs, skip-levels) and relationship stage (new, stable, strained)
- Current 1:1 cadence and what’s not working (2–5 concrete examples)
- What you want to change (coaching, feedback, career growth, wellbeing, alignment, retention)
- Constraints: meeting load, confidentiality/PII rules, any HR policies, time box/deadline
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.8 KB
- eval/with_skill.md 37 KB
- eval/without_skill.md 32 KB
- README.md 1.3 KB
- references/CHECKLISTS.md 2.0 KB
- references/EXAMPLES.md 958 B
- references/INTAKE.md 2.0 KB
- references/RUBRIC.md 2.8 KB
- references/SOURCE_SUMMARY.md 1.8 KB
- references/TEMPLATES.md 4.7 KB
- references/WORKFLOW.md 5.1 KB
- skillpack.json 382 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.
- 9d ago First seen · 138 lines · 40 tokens per session scan A d92e3c4a57f3
running-effective-1-1s is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 2,268 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-09-03.
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.".
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
recipe-plan-weekly-schedule
Review your Google Calendar week, identify gaps, and add events to fill them.
recipe-review-overdue-tasks
Find Google Tasks that are past due and need attention.