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 jaredlangleycc/nightshift-os --skill follow-up-trackergit clone --depth 1 https://github.com/jaredlangleycc/nightshift-osWrote 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/jaredlangleycc/nightshift-os/follow-up-tracker)<a href="https://agentmods.dev/skills/jaredlangleycc/nightshift-os/follow-up-tracker"><img src="https://agentmods.dev/badge/skills/jaredlangleycc/nightshift-os/follow-up-tracker/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/jaredlangleycc/nightshift-os/follow-up-tracker"><img src="https://agentmods.dev/badge/skills/jaredlangleycc/nightshift-os/follow-up-tracker.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.00107 | $0.03453 |
| Opus 5 | $0.00053 | $0.01726 |
| Sonnet 5 | $0.00021 | $0.00691 |
| Haiku 4.5 | $0.00011 | $0.00345 |
Grade A, and why
follow-up-tracker 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Follow-up Tracker
The graveyard of solo-business pipelines is the prospect who went silent and got forgotten. This skill is the weekly sweep that surfaces them.
It reads the user's CRM (HubSpot, Google Sheet, Notion, whatever they use), finds prospects who have not moved stage in 14+ days, classifies them by stage and stuck-pattern, and drafts the next-touch email per stage in the user's voice.
It NEVER auto-sends. The user reads, edits if needed, sends. The skill exists to remove the "find them" friction, so the only remaining work is the human judgment call.
When this skill triggers
- "Run follow-ups"
- "Draft follow-ups"
- "Who needs a nudge this week"
- "Check stale deals"
- "Stale pipeline sweep"
- "Find prospects gone cold"
- "Weekly follow-up sweep"
- "Anyone I forgot to nudge"
Triggered automatically on Friday mornings if weekly-brief skill is wired to it.
The 4-step sweep
Step 1: Read the CRM state
Pull the user's CRM. Source depends on stack:
- HubSpot: query deals where
last_modified > 14 days agoANDdealstage != closed_won AND != closed_lost. Pull associated contacts. - Google Sheet: scan the Pipeline tab for rows where
last_touch_dateis more than 14 days old andstageis not "won" or "lost". - Notion: query the pipeline database with filter
Last Edited Timemore than 14 days ago. - Airtable: same pattern, filter on Last Modified.
If user has no CRM, ask them to paste their pipeline list (name + stage + last-touch date + 1-line context per prospect). Then proceed manually.
Step 2: Classify by stage and pattern
Group the stale prospects by stage. Standard stages (adjust to user's pipeline):
- Lead: has not yet booked a call
- Discovery Booked: call scheduled but not yet held
- Discovery Held: call happened, no proposal yet
- Proposal Sent: proposal out, no decision
- Verbal Yes: they said yes but have not signed/paid
Within each stage, classify the stuck-pattern:
- No reply: user sent a message, prospect did not respond
- Awaiting prospect action: prospect said they'd send something, did not
- Awaiting user action: user said they'd send something, did not (THIS IS ON THE USER, flag it explicitly)
- Vague punt: "let's reconnect next quarter" with no specific trigger
What ships with it
2 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 · 326 lines · 107 tokens per session scan A 02ef23cb9fb5
follow-up-tracker is a skill published in the GitHub repository jaredlangleycc/nightshift-os (3 stars, last pushed 1mo ago), licensed MIT. It adds 107 tokens to every session and 3,453 once invoked, about $0.0005 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
Brand Guidelines Generator
Create and maintain brand style guides for consistent visual identity.
web-vid
Turn a web app or marketing site into a recreated (not screen-recorded) Remotion promo video — pixel-faithful to the site's own design system, choreographed clicks/scrolls/zooms, rendered to MP4. Use when the user asks for a product demo video, a promo/teaser for LinkedIn or social, an "walkthrough video" of their…
pitchdocs
Generate marketing-quality repository documentation from codebase analysis. Scans 10 signal categories, extracts features with file-level evidence, and produces README, CHANGELOG, ROADMAP, and 15+ more docs. Zero runtime dependencies. For AI context file management, see ContextDocs.
demo-video-factory
Generate a custom 26s product-demo video from any SaaS URL — brand-matched scenes, a recreated product-UI "wow" scene, real screenshots, and a soundtrack. Use whenever the user wants a demo, promo, launch, or marketing video for a website or product.
brand
Brand context management for marketing sessions with continuity across conversations.
liking-factor-engineer
Analyze and engineer liking to increase rapport, persuasion, and compliance in marketing, sales, and communication contexts. Use this skill when the user wants to improve how much an audience likes them, their brand, or their message — including writing sales copy, designing onboarding flows, crafting brand voice…