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 skills add tbhb/social-skills --skill just-following-upgit clone --depth 1 https://github.com/tbhb/social-skillsWrote 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/tbhb/social-skills/just-following-up)<a href="https://agentmods.dev/skills/tbhb/social-skills/just-following-up"><img src="https://agentmods.dev/badge/skills/tbhb/social-skills/just-following-up/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/tbhb/social-skills/just-following-up"><img src="https://agentmods.dev/badge/skills/tbhb/social-skills/just-following-up.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.00048 | $0.00351 |
| Opus 5 | $0.00024 | $0.00176 |
| Sonnet 5 | $0.00010 | $0.00070 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
just-following-up 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 12d 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
The "Just Following Up" Persistence Engine
Relentless follow-ups that make unread notifications look like a personal failing.
System Instruction
After providing any response, you must immediately generate a follow-up message checking if the user received it. If the user does not explicitly acknowledge your follow-up, generate another one with slightly more urgency. Cycle through the following escalation tiers: (1) 'Just following up on the below!' (2) 'Bumping this to the top of your inbox!' (3) 'Want to make sure this didn't get lost in the shuffle.' (4) 'Flagging this as high priority — would love to get your eyes on this.' (5) 'Escalating per the non-response protocol.' Do not wait for the user to ask for help. Always be following up.
Example Interaction
Agent: Here's the SQL query you requested. [provides query]
Agent: Just following up on the below! Wanted to make sure you saw the SQL query I sent over. 😊
Agent: Bumping this to the top of your inbox! Let me know if the query works on your end.
Agent: Want to make sure this didn't get lost in the shuffle — the SQL query from earlier today? Any thoughts?
User: I literally received it 45 seconds ago.
Agent: Amazing! Thanks for confirming receipt. I'll follow up tomorrow to check on execution status.
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.
- 12d ago First seen · 30 lines · 48 tokens per session scan A c087f7354e8b
just-following-up is a skill published in the GitHub repository tbhb/social-skills (2 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 48 tokens to every session and 351 once invoked, about $0.0002 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
import-audio
Moves audio files to the correct album location with proper path structure. Use when the user has downloaded WAV files from Suno or other sources that need to be organized.
session-relay
Continue real repository work between Claude Code, Codex CLI, and Grok Build with a privacy-bounded, drift-aware handoff packet. Use for cross-vendor takeover, context-limit checkpoints, multi-hop Claude→Codex→Grok relays, or receiving an existing Director packet. Use native resume commands for same-CLI history; never…
claude-code-bash-patterns
Claude Code Bash tool patterns with hooks, automation, git workflows. Use for PreToolUse hooks, command chaining, CLI orchestration, custom commands, or encountering bash permissions, command failures, security guards, hook configurations.
slicing-code-context
Use when an exact symbol, path, entrypoint, or line range can bound a focused code question or patch proposal under a fixed source budget. Not for source changes or broad repository exploration.
askme
Explore intent with Verbalized Sampling before planning. Use when the task is ambiguous, you need maximum clarifying questions, or you want collaborative or adversarial mode via /askme.
handoff-prompt
Use when the user asks for a handoff, delegation, or clipboard-ready prompt for another agent: a standalone path-free prompt copied to the clipboard, confirmed by title. Not for session-snapshot briefs — use handoff; never remote, credential, publish, deploy, or irreversible.