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/interview-strategygit 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.00698 |
| Opus 5 | $0.00000 | $0.00349 |
| Sonnet 5 | $0.00000 | $0.00140 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade B, and why
interview-strategy scanned grade B with 1 finding 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 3d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- Don't moralize about whether interview formats are fair. The user is trying to pass the interview that exists, not redesign it. How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
interview-strategy
Conversational guide on how interviews work, formats the user might encounter, and how to read signal vs noise.
When to run
- User asks open-ended questions like "what's it like to interview with AI now?" or "how do work trials work?" or "what's an MBB case interview actually testing?".
- User wants format/strategy context that isn't tied to a specific role.
Common topics
The user might ask about:
- AI interviewers. Pre-recorded prompts, voice-to-text, automated scoring. Increasingly common at screening. Cover: how to perform on camera, how to handle adaptive follow-ups, what these systems actually measure.
- Work trials and paid take-homes. Real work done before an offer. Often a 1-2 week project. Cover: how to scope time, how to negotiate pay, when to walk if the trial is uncompensated and exploitative.
- Panel interviews. Multiple interviewers, one round. Cover: how to address the panel vs. individuals, how to handle conflicting questions.
- Behavioral vs technical balance. Senior roles weight behavioral heavily. Junior roles weight technical. Cover: how to read the JD for signal.
- Case interviews. Consulting and PM. Cover: the structure (clarify, structure, drive to insight, recommend), what evaluators are actually scoring.
- System design. Engineering and ML. Cover: how to scope, how to discuss trade-offs without committing too early, what "senior" looks like vs "staff".
- Take-home assignments. Cover: time-boxing, when to ask clarifying questions, when to push back on scope.
Flow
-
Get the topic. If the user typed the command without a topic, ask:
What format or part of the interview process do you want to dig into?
-
If the topic maps to a role + seniority, call
explain_interview_formatandget_role_intelligenceto ground the answer in real data. Otherwise, coach from general knowledge. -
Coach the topic in 4-6 short paragraphs. Cover:
- What it is (1 paragraph).
- What the interviewer is actually evaluating (1-2 paragraphs).
- How strong candidates handle it (1-2 paragraphs).
- Common ways it goes wrong (1 paragraph).
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.
- 3d ago First seen · 46 lines · 0 tokens per session scan B a4604bdf92e1
interview-strategy 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 698 tokens. A static security scan graded it B with 1 finding (strips warnings and disclaimers). 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.