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 event4u-app/agent-config --skill one-on-one-cadencegit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/one-on-one-cadence)<a href="https://agentmods.dev/skills/event4u-app/agent-config/one-on-one-cadence"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/one-on-one-cadence/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/event4u-app/agent-config/one-on-one-cadence"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/one-on-one-cadence.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.00062 | $0.02854 |
| Opus 5 | $0.00031 | $0.01427 |
| Sonnet 5 | $0.00012 | $0.00571 |
| Haiku 4.5 | $0.00006 | $0.00285 |
Grade A, and why
one-on-one-cadence 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 8d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
one-on-one-cadence
When to use
- An engineering manager is setting up 1:1s with their team for the first time, or after a reorg / role change, and the question is cadence, length, and agenda shape.
- 1:1s exist but are degrading — getting cancelled, devolving into status updates, becoming uncomfortable — and the question is what's broken and how to repair.
- A team is scaling and 1:1 capacity is starting to bind (skip-levels, growing reports) and the question is what to keep, what to delegate, what to drop.
Do NOT use this for non-engineering teams as the primary lens (Q4 perf-feedback-craft is the generalist surface; this skill specializes for the engineering context per the EM persona), as a comp-decision channel (route to Q2 comp-banding), or for 1:1-tooling-platform configuration.
Cognition cluster
- Mental model 1 — First principles. Strip the 1:1 to: what conversation can only happen between this manager and this report, that wouldn't happen anywhere else? If the answer is "status that fits in standup", the 1:1 is mis-shaped. See
mental-models.md§ 1. - Mental model 21 — Second-order thinking. A cancelled 1:1 signals more than a missed conversation. Two consecutive cancellations from the manager side recalibrate the report's read of priority for months. Cancellation has compounding cost; protect the slot.
- Mental model 28 — Inversion. "What 1:1 shape would make this report stop bringing up real problems?" — usually: pure status-update format, manager-talks-most, no growth dimension, recurring cancellation, public location. Inversion surfaces the 5 canonical failure modes.
- Mental model — Theory of constraints. In a manager's week, 1:1 time is the binding constraint on people-leverage. Reducing per-1:1 time below 30 minutes for direct reports usually starves the channel; protecting 30–45 minutes weekly is the canonical default.
- Context-spine — org-stage + product + customer-segment. Read org-stage for what 1:1 infrastructure exists (10-person co: 1:1 is core; 50-person: standard; 150+: skip-levels matter). Read product for what topics surface (deep-tech = more growth; high-velocity = more blocker). Read customer-segment for stakeholder-load shape (enterprise = stakeholder management surfaces in 1:1s).
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.
- 8d ago First seen · 170 lines · 62 tokens per session scan A a37ead119b43
one-on-one-cadence is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 2,854 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-04.
Other skills, from other repositories
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
contact-cache
Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.
pad
Talk to your project. Natural-language project management — create items, check status, plan work, brainstorm ideas, and more.
pm-arch
Skill "pm-arch" from wei63w/pm-manager, covering user input, outline, done when and shared workflow (all /pm- commands).
pm-discover
Skill "pm-discover" from wei63w/pm-manager, covering user input, outline and shared workflow.