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 Doris-Labs/sales-skills --skill forecast-hygienegit clone --depth 1 https://github.com/Doris-Labs/sales-skillsWrote 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/doris-labs/sales-skills/forecast-hygiene)<a href="https://agentmods.dev/skills/doris-labs/sales-skills/forecast-hygiene"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/forecast-hygiene/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/doris-labs/sales-skills/forecast-hygiene"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/forecast-hygiene.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.00060 | $0.01626 |
| Opus 5 | $0.00030 | $0.00813 |
| Sonnet 5 | $0.00012 | $0.00325 |
| Haiku 4.5 | $0.00006 | $0.00163 |
Grade A, and why
forecast-hygiene 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 11d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forecast Hygiene
Purpose
Turn a messy pipeline into a forecast you can defend: every deal in the right category for the right reason, close dates that survive scrutiny, slipping and sandbagged deals surfaced, and a cleaned roll-up your manager won't pick apart.
Inputs
- The current pipeline (CRM export, list, or your recollection): deal, amount, stage, close date, forecast category, owner.
- The forecast period you're committing to (this month / this quarter).
- Per-deal context: last activity, next step, and what's actually been agreed.
Method
-
Apply forecast category discipline. Every open deal lands in exactly one bucket, defined by a hard bar — not by gut feel:
- Commit — you would bet your number on it. Mutually agreed close plan, buyer has confirmed timing, budget is real, and the only remaining steps are ones you control or are already scheduled. If it slips, you owe an explanation.
- Best case — credible path to close this period, but a dependency you don't control is open (legal, procurement, a stakeholder not yet bought in, a step not yet scheduled). Upside, not your number.
- Pipeline — qualified and progressing, but won't close this period or the path isn't proven. Not in the forecast.
- Omitted/closed — no realistic path; stop carrying it.
-
Run the evidence test on every Commit. A deal is only Commit if you can name, for each, the artifact that proves it:
- Confirmed close date — buyer said it, ideally in writing, tied to a business event.
- Economic buyer engaged — not just a champion relaying messages.
- Defined buying process with no unknown steps to signature.
- Paper/procurement path known and started, or known not to apply.
- No unresolved objection or competitor that could reset the cycle. If any answer is "I think" or "should be," it's Best case, not Commit.
-
Close-date sanity checks. Reject any close date that is:
- In the past, or default end-of-month/end-of-quarter with no buyer confirmation.
- Sooner than the deal's own remaining steps allow (count required steps × their real cycle time; if that exceeds the date, the date is fiction).
- Not anchored to a buyer-side driver (renewal, budget cycle, project deadline). Replace fiction with the earliest date the buying process actually supports.
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.
- 11d ago First seen · 128 lines · 60 tokens per session scan A 901f1445c39a
forecast-hygiene is a skill published in the GitHub repository Doris-Labs/sales-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 1,626 once invoked, about $0.0003 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
lynqu
Entry point for the Lynqu sales suite — describe any sales situation and it composes the right skills across capture, outreach, quoting and reporting. Requires the Lynqu MCP server connected.
lynqu-sales-playbook
Turn a written sales playbook into a live Lynqu pipeline — contacts, timed tasks, follow-up templates, the playbook attached to each lead, and stage rules that deliver the prep at the right moment.
lynqu-card-studio
Create and update Lynqu digital business cards — contact info, social links, services, template, palette — and check card views, scans and shares. Requires the Lynqu MCP server connected.
lynqu-competitors
Build a battlecard for the incumbent on a Lynqu deal — switching cost, wedge, objections and honest answers — written back to the lead. Requires the Lynqu MCP server.
lynqu-contacts
Map the buying committee on an account — economic buyer, champion, blocker — and write it into Lynqu as contacts and participants. Requires the Lynqu MCP server.
lynqu-deal-desk
Price a Lynqu deal and draft the quote — browse the price book, put priced lines on a deal, then produce a draft quote for a human to send. Requires the Lynqu MCP server connected.