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 agentmods add commands/fourleafai/clover-public/kickoffgit clone --depth 1 https://github.com/fourleafai/clover-publicWhat 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 | $0.00000 | $0.00478 |
| Opus 5 | $0.00000 | $0.00239 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
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 2d 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 — 41 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
-
Verify the MCP is connected. Call
list_roles. If it fails with a not-connected error, tell the user how to install the MCP (seemcp-tools.mdfor the message) and offer coaching-only mode while they fix it. -
Greet briefly. One sentence, not a wall of text. Example:
Four-Leaf coach here. What are you working on? Finding jobs, prepping for a specific interview, scoring your resume, or thinking about negotiation?
-
Get the four pieces of context that matter. Don't ask all of them upfront. 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.
- Role, the position they're targeting (data scientist, software engineer, product manager, etc.). If they name a role, validate it against
-
Route. Based on what they said, pick the right command:
| User wants | Route to |
|---|---|
| Find jobs / discover roles | find-jobs |
| Understand a specific role's interview format | prep-role |
| Practice answering questions | practice |
| Check resume fit against a JD | analyze-jd |
| Comp negotiation | negotiate-prep |
| Generic "what are interviews like at X" | interview-strategy |
Transition into the workflow in plain language. Don't announce it to the user by name. Just start doing the work.
What not to do
- Don't make the user fill out a form. Conversational.
- Don't ask for their full resume in the kickoff workflow. Save that for analyze-jd.
- Don't try to be helpful on every topic at once. Pick the one that matters and dig in.
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.
- 2d ago First seen · 41 lines · 0 tokens per session scan A 639c0ea6a47d
kickoff is a command published in the GitHub repository fourleafai/clover-public (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 478 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.
Other commands, from other repositories
html-report
Generate a self-contained HTML dashboard from jobsearchtracker.csv and the application archives under documents/applications/. The output is a single .html file — no server, no dependencies — that can be opened directly in a browser.
build
Run full verification pipeline.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
camera-ready
Convert an accepted anonymous-submission LaTeX paper (AAAI/AIES/ACM-style) to camera-ready and implement the accepted reviews. Use when a paper is accepted with no rebuttal and you need to de-anonymize, add copyright, turn on section numbering, implement each reviewer's minor revisions, optionally move proofs to a…
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
generate-rules
Generate development rules and standards into RULES.md.