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/extrasmall0/dear-hiring-managerWrote 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/extrasmall0/dear-hiring-manager/apify-collect)<a href="https://agentmods.dev/commands/extrasmall0/dear-hiring-manager/apify-collect"><img src="https://agentmods.dev/badge/commands/extrasmall0/dear-hiring-manager/apify-collect.svg" alt="Measured on agentmods" 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.00027 | $0.00092 |
| Opus 5 | $0.00014 | $0.00046 |
| Sonnet 5 | $0.00005 | $0.00018 |
| Haiku 4.5 | $0.00003 | $0.00009 |
Grade A, and why
apify-collect 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 8d 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
Use the apify-collect skill to gather job-posting URLs into urls.txt via Apify:
$ARGUMENTS
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.
- 8d ago First seen · 9 lines · 0 tokens per session scan A 6fffa437fdc2
apify-collect is a command published in the GitHub repository extrasmall0/dear-hiring-manager (107 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 92 once invoked, about $0.0001 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-30.
Other commands, from other repositories
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; request automation of…
labs-perplexity
Run a query using Perplexity's /labs mode via Playwright browser automation. Similar to /research-perplexity but uses Perplexity's experimental labs mode with a longer 15-minute timeout for complex queries.
auto-verify
A command for checking a website's front-end user experience with Playwright, a tool that automates web browsers.
batch-resume
Process multiple job descriptions from batchjds into tailored application packages.
submit-to-directories
Submit the product to the directory catalog in /.darkflow/directories.csv through a real browser, and track what has already been submitted.
interactive-dev
Start a persistent interactive development session with natural language browser control, auto-error monitoring, and full dev tool access.