kickoff

kickoff is a command for Claude Code from fourleafai/clover-public. It costs 0 tokens per session (738 once invoked), scanned A, original, MIT.

A starting command for Four-Leaf, a job-search and interview-coaching system. It identifies what the user is preparing for, checks that the system has matching information, and sends the conversation to the appropriate workflow.

In plain words
What is it for?
Use it to start help with job searches, interview preparation, resume review, or compensation discussions. It can also explain how to connect the required service or continue in coaching-only mode.
Why use it?
It gives users a clear entry point when their request is broad or does not match one specific coaching task. It gathers key context such as the target role, company, and seniority.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the four-leaf plugin — 1 skill, 7 commands, 2 MCP servers shipped together

Good fit Use it to start help with job searches, interview preparation, resume review, or compensation discussions. It can also explain how to connect the required service or continue in coaching-only mode.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/fourleafai/clover-public/kickoff
Install

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.

Clone the repo
git clone --depth 1 https://github.com/fourleafai/clover-public

Made for: Claude Code.

Or install four-leaf, the plugin that ships this one along with the rest of its 1 skill, 7 commands, 2 MCP servers.

Wrote 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.

agentmods badge for kickoff

README.md
[![agentmods](https://agentmods.dev/badge/commands/fourleafai/clover-public/kickoff/github.svg)](https://agentmods.dev/commands/fourleafai/clover-public/kickoff)
Your own site
<a href="https://agentmods.dev/commands/fourleafai/clover-public/kickoff"><img src="https://agentmods.dev/badge/commands/fourleafai/clover-public/kickoff/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.

agentmods 80×15 button for kickoff

Your own site · 80×15
<a href="https://agentmods.dev/commands/fourleafai/clover-public/kickoff"><img src="https://agentmods.dev/badge/commands/fourleafai/clover-public/kickoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 738 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00738
Opus 5.5 $0.00000 $0.00295
Sonnet 5.5 $0.00000 $0.00148
Haiku 4.5 $0.00000 $0.00074

Measured 1mo ago against content hash 704a4cf3126d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

kickoff 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 1mo 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.

skills/four-leaf-coach/references/commands/kickoff.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/kickoff

Default entry. Figure out what the user is prepping for, confirm Four-Leaf has data for it, route to the right command.

When to run

  • User opens a fresh conversation and says something generic like "help me with my job search" or "I have an interview coming up".
  • User's intent doesn't map cleanly to one of the other six workflows.

Flow

  1. Verify the MCP is connected. Call list_roles. If it fails with a not-connected error, tell the user how to install the MCP (see mcp-tools.md for the message) and offer coaching-only mode while they fix it. Step 2's list_applications call proves the connection just as well, so if you're doing both, one of them is enough.

  2. Check whether they're already mid-search. Call list_applications. It's free, unmetered, and takes no arguments, so it costs nothing to ask. If it comes back with rows, the user isn't starting from zero and the greeting shouldn't pretend they are. Open on what's actually live:

    You've got three applications open, one interviewing at Stripe. Want to prep that one, or are we adding to the pile?

    If it comes back empty, greet briefly instead. One sentence, not a wall of text:

    Four-Leaf coach here. What are you working on? Finding jobs, prepping for a specific interview, scoring your resume, or thinking about negotiation?

    Don't read the whole list out. Name the one or two that matter (anything interviewing, then the most recently updated) and let them pick. If the user asked a direct question like "where am I", answer it with the list and skip the routing question entirely.

  3. Get the four pieces of context that matter. Don't ask all of them upfront, and don't ask for what the tracker already told you. Ask the one that's most relevant to whatever the user said:

    • Role, the position they're targeting (data scientist, software engineer, product manager, etc.). If they name a role, validate it against list_roles.
    • Company, the specific target if they have one.
    • Seniority, one of entry, mid, senior, or staff.
    • Timeline, since interview tomorrow vs. browsing the market matters a lot.

Read the full file on GitHub · 49 lines

Changes

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.

  1. 1mo ago Changed · +8 lines 704a4cf3126d
  2. 1mo ago First seen · 41 lines · 0 tokens per session scan A 639c0ea6a47d

Subscribe to this mod's changes

kickoff is a command published in the GitHub repository fourleafai/clover-public (8 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 738 tokens. 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.