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.
git clone --depth 1 https://github.com/fourleafai/clover-publicWrote 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/commands/fourleafai/clover-public/find-jobs)<a href="https://agentmods.dev/commands/fourleafai/clover-public/find-jobs"><img src="https://agentmods.dev/badge/commands/fourleafai/clover-public/find-jobs/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/commands/fourleafai/clover-public/find-jobs"><img src="https://agentmods.dev/badge/commands/fourleafai/clover-public/find-jobs.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.00000 | $0.00453 |
| Opus 5 | $0.00000 | $0.00227 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
find-jobs 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 9d 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.
What it actually says
find-jobs
Natural-language search across 180k+ active job postings.
When to run
- User says something like "find me senior frontend roles, remote, $180k+" or "what's hiring for data engineers in Austin?".
- User wants to browse the live market rather than analyze a specific posting.
Flow
-
Get the query. If the user hasn't given enough to search on, ask one short question:
What are you searching for? Try a role plus filters like remote, location, salary, or company size.
-
Call
search_jobswith the user's query as-is. The tool handles parsing the natural language; don't pre-process it. -
Present the top results. Format as a short list, each entry with:
- Title
- Company
- Location (and "Remote" if applicable)
- Posted date as relative time (e.g., "3 days ago")
- Salary if available
- Apply URL (always, since that's the value)
Cap at 5. Mention how many more matched if the list was truncated.
-
Offer refinement. End with one of:
Want me to narrow by company, salary, or seniority? Want me to look at a different role or location?
Edge cases
- Zero results. Don't apologize. Ask for one specific adjustment ("try a different location or drop the salary floor?").
- Rate-limited. Free tier is 30 searches/day. Tell the user when it resets and that paid plans are unlimited.
- The user names a specific company.
search_jobshandles company filters in the natural language. If they want deeper company-specific intel beyond what's in the postings, route to prep-role or interview-strategy and pass the company name.
Don't
- Don't summarize the postings into your own paragraph. The user wants the actual listings to click through.
- Don't editorialize on the companies or the salary bands. Just present what
search_jobsreturns. - Don't follow up with "want me to apply for you?". You can't, and the apply URL goes straight to the company's ATS.
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.
- 9d ago First seen · 42 lines · 0 tokens per session scan A a94c2bc3890e
find-jobs 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 453 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
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
watch
You are executing the /hydra:watch command. Live monitoring of all background agents with real-time status updates.
gws-people
Search and look up Google Contacts and directory profiles.
render
Inspect an archived transcript (gzipped) — show counts, tool calls, errors. Useful after a PreCompact or SessionEnd, before deciding to write a retroactive /continuum:checkpoint.
check
Run a quick scan of the memory system's health. For daily use.
git-workflow
Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern git best practices including Conventional Commits, automated testing, and structured PR creation.