follow-up-radar

follow-up-radar is a skill for Codex from jqaisystems/jqai-ai-skills. It costs 72 tokens per session (789 once invoked), scanned A, original, MIT.

A follow-up tracker for outreach or customer-relationship files stored as Markdown documents. It finds overdue contacts and prepares messages without sending them.

In plain words
What is it for?
Use it to scan a folder, list overdue follow-ups from oldest to newest, and draft messages for the people you still need to contact.
Why use it?
It removes the need to check each contact file manually or remember who needs a reply. You get a report before any drafts are made.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to scan a folder, list overdue follow-ups from oldest to newest, and draft messages for the people you still need to contact.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jqaisystems/jqai-ai-skills/follow-up-radar
Install

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.

Any agent
npx skills add jqaisystems/jqai-ai-skills --skill follow-up-radar
Clone the repo
git clone --depth 1 https://github.com/jqaisystems/jqai-ai-skills

Made for: Codex.

Wrote 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.

agentmods badge for follow-up-radar

README.md
[![agentmods](https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/follow-up-radar/github.svg)](https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/follow-up-radar)
Your own site
<a href="https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/follow-up-radar"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/follow-up-radar/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.

agentmods 80×15 button for follow-up-radar

Your own site · 80×15
<a href="https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/follow-up-radar"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/follow-up-radar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 789 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00072 $0.00789
Opus 5.5 $0.00029 $0.00316
Sonnet 5.5 $0.00014 $0.00158
Haiku 4.5 $0.00007 $0.00079

Measured 1mo ago against content hash c00302bb7260, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

follow-up-radar 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 1mo 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.

skills/follow-up-radar/SKILL.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Follow-up Radar

Most outreach dies not because the first email failed but because the follow-up never went out. This skill finds the follow-ups you owe and puts the drafts in front of you. It reports first and it never sends anything.

Step 0: Load the radar config (once)

Look for a follow-up-radar.config.md file in the project root. If it does not exist, ask for the values below, then offer to save them.

WATCH_FOLDER    Folder containing one markdown file per prospect or contact
STATUS_KEY      Frontmatter key holding the state (default: status)
DUE_KEY         Frontmatter key holding the follow-up date (default: follow_up_due)
DONE_VALUES     Status values that need no follow-up (default: Replied, Closed, Skip)
VOICE_NOTES     Optional tone guidance for drafts

The expected file shape is simple frontmatter, for example:

---
company: Example Studio
status: Sent
follow_up_due: 2026-05-01
---

If the user's files use different keys, map them in the config instead of asking them to change their files.

Step 1: Scan and report

Read the frontmatter of every markdown file in WATCH_FOLDER. Build the report before drafting anything:

# Follow-up Radar: <today>

## Overdue (oldest first)
| Contact | Status | Due | Days overdue | File |
|---|---|---|---|---|

## Due in the next 7 days
| Contact | Status | Due | File |
|---|---|---|---|

## Waiting, not yet due: N
## Done or closed: N
## Files with missing or unparseable dates: <list them, do not guess>

Show the report in chat. If nothing is overdue, say so in one line and stop unless asked to continue.

Step 2: Draft the overdue follow-ups

Only after the user confirms, or if they asked for drafts upfront. For each overdue item, oldest first:

  1. Read the full file. If it already contains a prepared follow-up draft, use it as the base and only refresh anything stale (dates, references to "last week").
  2. If there is no draft, write one: 80 words max, references the first message in one clause, adds one new angle or piece of value, no guilt-tripping, no "just checking in".
  3. Subject line is Re: plus the original subject when the original is in the file.
  4. Present each draft in chat under the contact's name with the file path.

Read the full file on GitHub · 79 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 1mo ago First seen · 79 lines · 72 tokens per session scan A c00302bb7260

Subscribe to this mod's changes

follow-up-radar is a skill published in the GitHub repository jqaisystems/jqai-ai-skills (3 stars, last pushed 13d ago), licensed MIT. It adds 72 tokens to every session and 789 once invoked, about $0.0003 per session on Opus 5.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.

Related

Other skills, from other repositories

reins

Drive the user's real, logged-in browser from the shell via the reins CLI. Because it's their actual browser, every site is already authenticated — so you can scrape behind logins, read cookies/tokens/localStorage, watch and replay live API traffic, call a site's own API as the signed-in user, and…

karnstack/reins · 98 tokens

baoyu-comic

A tool for creating original educational comics that explain knowledge or ideas through multiple illustrated panels. It supports different art styles and tones and can create several comics in one batch.

JimLiu/baoyu-skills · 61 tokens

baoyu-diagram

Create professional, dark-themed SVG diagrams of any type — architecture diagrams, flowcharts, sequence diagrams, structural diagrams, mind maps, timelines, illustrative/conceptual diagrams, and more. Use this skill whenever the user asks for any kind of technical or conceptual diagram, visualization of a system…

JimLiu/baoyu-skills · 146 tokens

playwright-cli

Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…

testdino-hq/playwright-skill · 64 tokens

spring-boot-team-harness

Use when a team wants every developer's coding agent (Claude Code or Codex) to follow the same rules on a Maven Spring Boot 4 repository: setting up AGENTS.md, guardrails, shared agent settings, or build and CI checks that agents must pass before code merges. It adds ./mvnw verify gates that fail on null-safety bugs…

a-pavithraa/springboot-skills-marketplace · 132 tokens

agent-wiki

Incremental LLM-friendly wiki generator for Obsidian note vaults. Use when: (1) Building wiki from notes, (2) Ingesting notes to wiki, (3) Obsidian LLM wiki, (4) Incremental knowledge base management. Triggers: 'build wiki from notes', 'ingest notes to wiki', 'Obsidian LLM wiki', 'incremental knowledge base'.

Dianel555/DSkills · 89 tokens