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 jeffreytse/grimoire-core --skill run-one-on-onegit clone --depth 1 https://github.com/jeffreytse/grimoire-coreWrote 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/jeffreytse/grimoire-core/run-one-on-one)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/run-one-on-one"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-one-on-one/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/jeffreytse/grimoire-core/run-one-on-one"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-one-on-one.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.00023 | $0.00873 |
| Opus 5 | $0.00012 | $0.00436 |
| Sonnet 5 | $0.00005 | $0.00175 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
run-one-on-one 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 7d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run One-on-One
Make every 1:1 a high-signal conversation that builds trust, surfaces problems early, and develops the direct report.
Why This Is Best Practice
Adopted by: Manager Tools methodology used by 5M+ managers; Andy Grove formalized 1:1s at Intel as a core management tool Impact: Gallup research shows that managers who hold regular 1:1s reduce voluntary turnover by up to 25% and improve engagement scores by 3× compared to ad-hoc check-ins
Why best: The 1:1 is the primary tool for a manager to learn what is actually happening on the ground. It belongs to the direct report, not the manager — inverting the usual power dynamic creates psychological safety and honest reporting.
Steps
- Schedule at a fixed time — Same day, same time, weekly. Treat cancellation as a last resort. Consistency signals that the person matters.
- Prepare a shared agenda doc — Both parties add items before the meeting. The direct report's items go first. Use a running doc so nothing is lost between weeks.
- Open with the direct report's topics — Ask "What's on your mind?" and let them lead for the first half. Do not fill silence with your own agenda.
- Listen for signals under the surface — Note frustration, disengagement, or repeated themes. Ask clarifying questions: "Tell me more about that" and "What would make this better?"
- Cover your own topics in the second half — Feedback, context, blockers you can remove, strategic direction. Be specific and brief.
- Deliver feedback in SBI format — Situation, Behavior, Impact. "In Tuesday's design review [S], you interrupted two teammates [B], which shut down ideas before we heard them [I]."
- Close with one commitment each — Both parties name one concrete action before the next 1:1. Write it in the shared doc.
Rules
- The 1:1 is the direct report's meeting, not the manager's status update.
- Never cancel; reschedule the same day if unavoidable.
- Keep notes in a shared doc both parties can read and add to.
- Do not use the 1:1 to deliver surprise performance news — that requires a separate conversation.
- Rotate between professional development, project work, and personal check-in topics across weeks.
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.
- 7d ago First seen · 53 lines · 23 tokens per session scan A 478d1ee055b9
run-one-on-one is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 21d ago), licensed MIT. It adds 23 tokens to every session and 873 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-09-03.
Other skills, from other repositories
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
make-skill-template
Create new Agent Skills for GitHub Copilot from prompts or by duplicating this template. Use when asked to "create a skill", "make a new skill", "scaffold a skill", or when building specialized AI capabilities with bundled resources. Generates SKILL.md files with proper frontmatter, directory structure, and optional…
meeting-efficiency
Agenda design, time boxing, decision capture, async alternatives, and productive facilitation.
deep-work-optimization
Focus blocks, distraction management, and flow state triggers for cognitively demanding work.
disagreement-protocol
Canonical phrasing for respectful disagreement without capitulation — structural resistance to sycophancy.
opt-in-workspace-writes
Extensions/tools that auto-write to user workspaces without consent.