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 pipeline-reviewgit 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/pipeline-review)<a href="https://agentmods.dev/skills/jaredlangleycc/nightshift-os/pipeline-review"><img src="https://agentmods.dev/badge/skills/jaredlangleycc/nightshift-os/pipeline-review/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/pipeline-review"><img src="https://agentmods.dev/badge/skills/jaredlangleycc/nightshift-os/pipeline-review.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.00102 | $0.03163 |
| Opus 5 | $0.00051 | $0.01581 |
| Sonnet 5 | $0.00020 | $0.00633 |
| Haiku 4.5 | $0.00010 | $0.00316 |
Grade A, and why
pipeline-review 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.
How it starts
The opening of the file, as written. The whole thing — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Review
Weekly stage-by-stage audit of the user's sales pipeline. Different from the follow-up sweep (which is prospect-by-prospect): pipeline review goes one level higher and audits the SHAPE of the pipeline.
It surfaces: stage drift (deals stuck at same stage 3+ weeks), no-movement clusters (5+ deals at same stage), missing next-action dates (deals with no committed follow-up), stage-progression issues (deals skipping stages or sliding backwards), forecast accuracy gaps, and ICP-fit dilution.
The output is a diagnostic 1-pager: where the pipeline is healthy, where it's bleeding, and 3-5 deals that need specific user action this week.
When this skill triggers
- "Run the pipeline review"
- "Audit my pipeline"
- "Pipeline check"
- "Deals review"
- "Weekly pipeline"
- "Where am I bleeding deals"
- "Pipeline health"
- "Show me where the pipeline is broken"
- "Friday pipeline"
Best run weekly, ideally Friday morning. Can be run monthly if pipeline volume is low (under 20 active deals).
The 6-section audit
Section 1: Pipeline snapshot (top)
Headline numbers for fast scanning:
PIPELINE REVIEW: [date]
TOTAL ACTIVE DEALS: N
TOTAL PIPELINE VALUE: $X
DEALS THIS WEEK (closed won + lost): N won, N lost
BY STAGE:
- Lead: N deals, $X
- Discovery Booked: N deals, $X
- Discovery Held: N deals, $X
- Proposal Sent: N deals, $X
- Verbal Yes: N deals, $X
Reader gets the math in 10 seconds.
Section 2: Stage health check
For each stage, evaluate:
Velocity: average days in stage before progression (or current pipeline) Conversion rate: of deals that entered this stage, what % progressed vs got stuck or lost Volume: is the stage starving (too few) or bloated (too many)?
Healthy benchmarks (adjust for offer + cycle length):
| Stage | Healthy avg days | Healthy conversion to next | Bloat threshold |
|---|---|---|---|
| Lead | 7-14 days | 30-50% | >30 deals |
| Discovery Booked | 0-7 days | 70-85% (show rate) | >5 deals |
| Discovery Held | 7-14 days | 30-50% to proposal | >10 deals |
| Proposal Sent | 7-21 days | 30-50% close rate | >5 deals |
| Verbal Yes | 0-7 days | 90%+ close rate | >3 deals |
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.
- 12d ago First seen · 333 lines · 102 tokens per session scan A ecee237978dc
pipeline-review is a skill published in the GitHub repository jaredlangleycc/nightshift-os (3 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 3,163 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…