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 ship-it-fridaygit 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/ship-it-friday)<a href="https://agentmods.dev/skills/jaredlangleycc/nightshift-os/ship-it-friday"><img src="https://agentmods.dev/badge/skills/jaredlangleycc/nightshift-os/ship-it-friday.svg" alt="Measured on agentmods" 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.00132 | $0.04608 |
| Opus 5 | $0.00066 | $0.02304 |
| Sonnet 5 | $0.00026 | $0.00922 |
| Haiku 4.5 | $0.00013 | $0.00461 |
Grade A, and why
ship-it-friday 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 8d 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 — 458 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship It Friday
The weekly close-out ritual. The handoff between this week and next.
Solopreneurs without a Friday close-out lose the compounding effect of weekly rhythm. The week ends in drift. Monday starts in fog. Ship-it-friday is the ritual that turns Friday into a real handoff so Monday opens in a queue.
This skill does not produce new work. It calls four other skills in sequence and ties their output into a single close-out log.
When this skill triggers
/ship-it-friday/friday-close/friday-wrap-up/close-out-the-week/end-of-week/week-recap- "Ship it Friday"
- "Close out the week"
- "Friday wrap up"
- Optional cron: scheduled task on Friday 5pm local (user opts in via CLAUDE.md)
The orchestration
Run these in order. Each step delegates to a dedicated skill. Capture each step's output into the final log.
Step 1: Decision-logger (this week's decisions)
Call decision-logger to surface all decisions logged in the last 7 days. The skill returns a list of:
- Decision title
- Decision date
- One-line summary
- Revisit date (if set)
The user reviews. The user can add a decision they did not log mid-week ("I decided not to take the Acme deal, log it now"). The skill writes any new entries.
Output to capture for the close-out log:
## Decisions logged this week
- 2026-05-19: Override family floor for Alex discovery call
- 2026-05-20: Kill Blotato subscription (cancel May 29)
- 2026-05-21: Ship Trust the Process essay Sun May 24
- 2026-05-23 (new): Pass on Acme partnership (timing not right)
Step 2: File-sweep
Call file-sweep. The skill runs the six-task weekly sweep and returns a short summary.
Capture summary for the close-out log:
## File sweep
- Inbox files sorted: 7
- Stale drafts flagged: 4
- Backups rotated: 3 days → cold archive
- Loose root files surfaced: 1
- Cloud sync: 2 uploads
Log: reports/file-sweep-2026-W21.md
Do not re-print the full file-sweep log here. The link suffices.
What ships with it
3 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.
- 8d ago First seen · 458 lines · 0 tokens per session scan A 47e29fd84789
ship-it-friday is a skill published in the GitHub repository jaredlangleycc/nightshift-os (3 stars, last pushed 1mo ago), licensed MIT. It adds 132 tokens to every session and 4,608 once invoked, about $0.0007 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
recipe-plan
Create work plan from design document and obtain plan approval.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
recruit-init
Uma habilidade que prepara um espaço de trabalho para recrutamento, com pastas, documentos de referência, registros e instruções para agentes de programação. Ela verifica dependências como Node.js, ferramentas de vagas e, opcionalmente, o Feishu.
revenue-team-onboarding
Revenue team onboarding — security access provisioning, ramp schedules, 30-60-90 plans, Slack engagement, shadowing, certification, and time-to-first-meeting reduction. Use when onboarding SDRs, AEs, managers, or RevOps hires. Triggers on: "sales onboarding", "SDR ramp", "30-60-90 sales", "reduce ramp time", "Slack…
job
Daily routines for a corporate software engineering job. Start mode triages the inbound review queue, your own open PRs, and the issue tracker's plan for today. End mode clears the outbox, surfaces review debt, sweeps worktrees for unpushed work, and tidies tracker state for tomorrow. Use via /job, /job start, /job…