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 camilooscargbaptista/cto-toolkit --skill one-on-onegit clone --depth 1 https://github.com/camilooscargbaptista/cto-toolkitWrote 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/camilooscargbaptista/cto-toolkit/one-on-one)<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/one-on-one"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/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/camilooscargbaptista/cto-toolkit/one-on-one"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/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.00122 | $0.01113 |
| Opus 5 | $0.00061 | $0.00557 |
| Sonnet 5 | $0.00024 | $0.00223 |
| Haiku 4.5 | $0.00012 | $0.00111 |
Grade A, and why
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 10d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
1:1 Meeting Prep & Notes
Great 1:1s are the highest-leverage activity a CTO has. They build trust, surface problems early, unblock people, and develop future leaders. This skill helps you prepare for and document them effectively.
1:1 Prep Template
Before each 1:1, quickly fill this out (5 min max):
# 1:1 Prep: [Person] — [Date]
## Their Context
- Current project/focus: [What are they working on?]
- Recent wins: [Ship something? Solve a hard problem?]
- Potential concerns: [Blockers, frustration signals, team dynamics?]
## My Agenda (pick 1-2, not all)
- [ ] Check in on [specific project/task]
- [ ] Give feedback on [specific behavior/output]
- [ ] Discuss [growth opportunity / career topic]
- [ ] Address [concern / issue]
## Questions to Ask
- [Open-ended questions, not yes/no]
- [Focus on their perspective, not yours]
## Key Message
[If there's ONE thing they should take away from this meeting, what is it?]
1:1 Notes Template
# 1:1 Notes: [Person] — [Date]
## Key Takeaways
- [Most important things discussed]
## Action Items
- [ ] [Owner]: [Specific action] — by [date]
- [ ] [Owner]: [Specific action] — by [date]
## Follow-up Topics
- [Things to revisit next time]
## Signals to Watch
- [Engagement, energy, concerns detected]
Types of 1:1 Conversations
Regular Check-in
Focus: Their priorities, blockers, and wellbeing.
Good questions:
- "What's the most important thing you're working on this week?"
- "What's slowing you down?"
- "Is there anything you need from me?"
- "How's the team dynamic feeling?"
Feedback Conversation
Structure: SBI (Situation-Behavior-Impact)
- Situation: "In yesterday's sprint review..."
- Behavior: "...you presented the technical trade-offs before recommending a solution..."
- Impact: "...which helped the team make an informed decision and got buy-in faster."
For constructive feedback, add:
- Request: "Going forward, I'd like to see [specific change]."
- Then ask: "What do you think? Does that resonate?"
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.
- 10d ago First seen · 120 lines · 122 tokens per session scan A 3ee71d196755
one-on-one is a skill published in the GitHub repository camilooscargbaptista/cto-toolkit (7 stars, last pushed 5mo ago), licensed MIT. It adds 122 tokens to every session and 1,113 once invoked, about $0.0006 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-31.
Other skills, from other repositories
run-difficult-conversation
Use when preparing for or facilitating a high-stakes conversation involving conflict, feedback, performance issues, or sensitive interpersonal topics.
run-one-on-one
Use when preparing for or improving weekly one-on-one meetings between a manager and a direct report.
offer-toolkit-skill
A set of job-search tools covering the path from finding a vacancy to accepting an offer. It includes separate tools for job searches, job-description analysis, tailored resumes, behavioral interviews, offer comparisons, and salary negotiation.
job-hunt-skill
A workflow for finding and maintaining a searchable list of job openings from LinkedIn and public websites. It can use a résumé, career goals, example job descriptions, or existing links to build the list.
team-motivation-ops
Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict…
mentor-patterns
The six patterns the Mentor hunts in the records to decide WHEN to speak. Silence is the default; only a real, recurring pattern earns a word. This skill gives the canonical detection method for each pattern (DB query + threshold) so the Mentor never speaks from a single data point. Read-only — never writes to the DB.…