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 fledgeling-co/fledgeling-plugins --skill household-follow-upgit clone --depth 1 https://github.com/fledgeling-co/fledgeling-pluginsWrote 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/fledgeling-co/fledgeling-plugins/household-follow-up)<a href="https://agentmods.dev/skills/fledgeling-co/fledgeling-plugins/household-follow-up"><img src="https://agentmods.dev/badge/skills/fledgeling-co/fledgeling-plugins/household-follow-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/fledgeling-co/fledgeling-plugins/household-follow-up"><img src="https://agentmods.dev/badge/skills/fledgeling-co/fledgeling-plugins/household-follow-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.00051 | $0.00518 |
| Opus 5.5 | $0.00020 | $0.00207 |
| Sonnet 5.5 | $0.00010 | $0.00104 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
household-follow-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 5d 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
Household follow-up
Read the evidence contract. Keep the request bounded to the selected orders or household tasks. Use supported mail/calendar/provider sources to discover identifiers, then confirm current carrier, retailer or appointment state. Do not collect unrelated inbox content.
Join order, shipment and item identities deliberately. A split order can have several shipments; one tracking event does not complete all of them. Deduplicate carrier updates and retailer notices while retaining both locators. Confirm the actual carrier and tracking id; similarly named vendors are not interchangeable. Use neutral aliases in the summary rather than repeating addresses or telephone numbers. Never put private order data in this reusable plugin.
Distinguish estimated arrival, dispatched, delivery attempt, carrier-reported delivery, received by the household, return requested, handed to carrier and refund posted. Carrier-reported delivery alone does not establish receipt when the user is asking about a missing parcel; a return label does not prove a refund. Resolve conflicting states at their authoritative source or mark them unverified. Relative dates need the relevant local timezone and an absolute date before they become reminders. Keep return eligibility and booking availability separate from whether the user wants to act.
For each open item, give the next cheapest useful step, its deadline/window,
owner, evidence and blocking fact. Prepare a local support-message draft,
return checklist or appointment options when useful. External sends, return
submission, booking, cancellations and purchases require authority for that
action; review-only requests do not grant it. Respect budgets, private locations
and already answered preferences. Use clarify:clarify for a deciding fact that
only the user can supply.
Stop after status reconciliation and the authorised outcome is observed, or after handing over named blockers. A requested reminder can be scheduled through supported tools once timezone, target and required access are resolved; creating the skill or finding a deadline does not authorise reminders. Check for an existing reminder so repeat runs do not create duplicates.
For resumable reviews, use the ledger format
with domain household; record receipt/refund completion at the source appropriate
to the requested outcome.
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.
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.
- 5d ago First seen · 46 lines · 51 tokens per session scan A b7dc797ecf88
household-follow-up is a skill published in the GitHub repository fledgeling-co/fledgeling-plugins (2 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 518 once invoked, about $0.0002 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-10-12.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…