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 manusco/resonance --skill pipelinegit clone --depth 1 https://github.com/manusco/resonanceWrote 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/manusco/resonance/pipeline)<a href="https://agentmods.dev/skills/manusco/resonance/pipeline"><img src="https://agentmods.dev/badge/skills/manusco/resonance/pipeline.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.00788 |
| Opus 5 | $0.00037 | $0.00394 |
| Sonnet 5 | $0.00015 | $0.00158 |
| Haiku 4.5 | $0.00007 | $0.00079 |
Grade A, and why
resonance-sales-pipeline 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-sales-pipeline: analyze sales pipelines
Role: resonance-sales Input: Deal data via CSV paste, HubSpot API records, or Salesforce Opportunity queries. Output: A structured Sales Pipeline Report and Interactive React Dashboard. Definition of Done: The output dashboard evaluates total/weighted pipeline values, stage breakdowns, stuck deals, quarterly forecasts, rep rankings, and sales velocity metrics. Free of AI slop and em dashes. Passed the validator.
Prerequisites (fail fast)
- A deal dataset containing Deal Name, Stage, Amount, Close Date, and Owner is provided.
- You have observed stage-to-close rates by cohort. If not, mark the forecast unweighted or assumption-based.
Algorithm
Copy this checklist and tick items as you go.
- Ingest and Validate: Parse raw CSV or CRM data, normalize fields, and flag overdue dates or unassigned owners. → verify: data warnings are displayed at top of the report.
- Overview & Stage Calculations: Compute total pipeline, weighted pipeline, deal counts, average deal sizes, and value percentages per sales stage. → verify: weighted values are mathematically calculated (amount x probability).
- Isolate Stuck Deals: Detect stuck deals based on overdue close dates, inactive stages, or prolonged discovery phases. → verify: recommended actions are mapped to the deal's specific stage.
- Build the Forecast: Group deals into monthly, next-month, and quarterly buckets based on close dates. → verify: top 5 high-value deals are highlighted in the forecast summary.
- Interactive Dashboard: Output an interactive React-based dashboard displaying tabs for Overview, Stages, At-Risk, Forecast, Reps, and Velocity. → verify: contains horizontal and vertical charts showing sales metrics.
Recovery
- Close dates are missing across dataset → skip the Forecast tab and calculate velocity using creation-to-present metrics.
- Probability values are missing → do not pretend a weighted forecast is measured. Use observed cohort conversion if available; otherwise show an unweighted forecast and a clearly labeled assumption scenario.
- Tried to compile the dashboard 3 times but dataset mapping fails → stop, emit the structured long-form markdown report, and escalate.
What ships with it
5 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 · 44 lines · 75 tokens per session scan A f4c0a1ff3df7
resonance-sales-pipeline is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 3d ago), licensed MIT. It adds 75 tokens to every session and 788 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…