Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add alwaysmap/jobs4me/plugin install jfmWrote 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/skills/alwaysmap/jobs4me/followup)<a href="https://agentmods.dev/skills/alwaysmap/jobs4me/followup"><img src="https://agentmods.dev/badge/skills/alwaysmap/jobs4me/followup/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/skills/alwaysmap/jobs4me/followup"><img src="https://agentmods.dev/badge/skills/alwaysmap/jobs4me/followup.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.00137 | $0.01943 |
| Opus 5 | $0.00068 | $0.00971 |
| Sonnet 5 | $0.00027 | $0.00389 |
| Haiku 4.5 | $0.00014 | $0.00194 |
Grade A, and why
followup 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Follow Up on Applied Roles
Shell setup: Always export JFM_DIR='<workspace path>' (single quotes) before running tracker commands. The script refuses to operate if it can't resolve a real workspace.
Read ../search/references/routing.md before processing any user message — it defines how to decompose compound messages and where to route each type of input.
This skill has two modes that share context and tone but serve different jobs:
- Mode 1 — Briefing. Invoked as
/jfm:followupwith no args. Produces a timing-aware briefing of every role in theappliedstage: what to do next on each one, why, and which actions cluster together this week. - Mode 2 — Single-role outreach drafting. Invoked as
/jfm:followup {company}. Runs a short validating conversation about one role, then drafts three templated outreach variants (cold hiring manager, warm intro ask, recruiter ping) and saves them to the role's directory alongside the cover letter.
Files
| File | Loaded when |
|---|---|
SKILL.md (this file) |
Always |
references/timing.md |
Mode 1 — cadence bands, override mechanism, days-since-applied source-of-truth, two-stage recommendation selection, follow-up-date stamping. |
references/mode-2-drafting.md |
Mode 2 only — single-role workflow, context-card protocol, validating conversation, template shape, save format. Skip entirely in Mode 1. |
references/example-output.md |
Mode 1 — sample briefing on a synthetic 6-role board, for shape reference. |
references/outreach-example.md |
Mode 2 — full file shape for {role_dir}/outreach.md. |
../search/references/routing.md |
First — before processing any user message. |
Hard constraint: data access goes through tracker.js
Every tracker / profile / filters read and write goes through scripts/tracker.js. The skill never parses tracker.yaml, profile.yaml, or filters.yaml directly — not even for reads. This keeps backups, validation, board rebuilds, and schema consistency centralized in one script.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 145 lines · 137 tokens per session scan A 59aa4c55513e
followup is a skill published in the GitHub repository alwaysmap/jobs4me (2 stars, last pushed 1mo ago), licensed MIT. It adds 137 tokens to every session and 1,943 once invoked, about $0.0007 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-31.
Other skills, from other repositories
job-application-agent
Finds, evaluates, fills, submits, and tracks a candidate's own job applications using a verified resume, evidence-based targeting, secure local profile storage, and browser automation. Use for onboarding or migrating a job-search profile, searching active roles, assessing a posting, applying to an authorized URL or…
apply
Apply to a single job (URL or pasted page) with fit review, or score and apply the job links pasted into an apply campaign when no argument is given.
scan-inbox
Classify unscanned mailbox messages, fuzzy-match each to an existing application, and write the proposal back. The user approves in /inbox.
resume-campaign
Resume a paused JobPilot campaign by id. Re-flips the campaign to inprogress and replays the apply loop on any remaining approved jobs without re-asking for fit confirmation.
autopilot-jobhunt
Run a job hunt in one agentic pass — scan configured company careers pages, score postings against the user's resume, draft a tailored resume + cover letter per chosen role (never applies), and export matches. Trigger when the user says /autopilot-jobhunt or asks to scan/find jobs or draft an application.
auto-job-apply
A job-application workflow that compares a job description with a resume and assigns an A, B, or C match grade.