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 NimbleBrainInc/upjack --skill follow-up-emailgit clone --depth 1 https://github.com/NimbleBrainInc/upjackWrote 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/nimblebraininc/upjack/follow-up-email)<a href="https://agentmods.dev/skills/nimblebraininc/upjack/follow-up-email"><img src="https://agentmods.dev/badge/skills/nimblebraininc/upjack/follow-up-email/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/nimblebraininc/upjack/follow-up-email"><img src="https://agentmods.dev/badge/skills/nimblebraininc/upjack/follow-up-email.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.00000 | $0.00359 |
| Opus 5 | $0.00000 | $0.00179 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
follow-up-email 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 10d 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
Follow-up Email
Draft and send contextual follow-up emails to contacts.
When to Use
- Weekly stale deal alert (triggered via schedule, Monday 10 AM)
- User asks to follow up with a contact
- After a meeting or call activity
Process
-
Gather context:
- Contact record (name, title, company, lifecycle stage)
- Recent activities with this contact
- Related deals and their status
- Previous emails sent
-
Determine email type:
- Initial outreach: First contact, introduce value proposition
- Meeting follow-up: Summary and next steps from recent meeting
- Deal follow-up: Check in on proposal or stalled deal
- Re-engagement: Reach out to cold contacts with new context
-
Draft the email:
- Subject line: Clear, specific, under 60 characters
- Opening: Reference last interaction or shared context
- Body: One clear ask or value proposition
- Closing: Specific next step with timeline
-
Send via email bundle (
email__send_email) -
Log an activity with the email content and outcome
Tone Guidelines
- Professional but conversational
- Short paragraphs (2-3 sentences max)
- One clear call to action per email
- Reference specific details to show personalization
- Never use generic templates without customization
Rules
- Check
last_contactedbefore sending — don't email someone contacted in the last 48 hours - For stale deal alerts, prioritize by deal value
- Always BCC the CRM (record the activity)
- Max 5 follow-up emails per contact before escalating to manual review
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.
- 10d ago First seen · 49 lines · 0 tokens per session scan A 74a1015ffd2b
follow-up-email is a skill published in the GitHub repository NimbleBrainInc/upjack (9 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 359 tokens. 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
kn-implement
Use when implementing a task - follow the plan, check ACs, track progress.
kn-spec
Use when creating a specification document for a feature (SDD workflow).
kn-flow
Use when orchestrating a full Knowns spec or task wave through planning, implementation, review, integration, and verification, optionally using sub-agents when scopes are parallel-safe.
kn-handoff
Use when a feature crosses repository boundaries and one side must hand work to the other - generates a self-contained frontend-to-backend brief or backend-to-frontend API contract.
kn-debug
Use when debugging errors, test failures, build issues, or blocked tasks — structured triage to fix to learn.
kn-plan
Use when creating an implementation plan for a task.