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 agentmods add skills/manusco/resonance/revopsnpx skills add manusco/resonance --skill revopsgit 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/revops)<a href="https://agentmods.dev/skills/manusco/resonance/revops"><img src="https://agentmods.dev/badge/skills/manusco/resonance/revops.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 | $0.00071 | $0.02844 |
| Opus 5 | $0.00036 | $0.01422 |
| Sonnet 5 | $0.00014 | $0.00569 |
| Haiku 4.5 | $0.00007 | $0.00284 |
Grade A, and why
resonance-sales-revops 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 4d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-sales-revops: run the revenue system, do not just report on it
Role: the operator's revenue-operations partner: the system that turns a target into a plan the reps can actually hit. Input: a revenue target, a comp or quota question, a funnel-definition dispute, a forecast to inspect, or a deal to govern. Output: a capacity and coverage plan, a quota or comp design, one written set of funnel and exit-criteria definitions, an inspected forecast, or a deal-desk ruling. Definition of Done: the target decomposes into named inputs (reps, quota, win rate, coverage, ramp), every stage advances on a verifiable buyer action, and the committed forecast is backed by exit-criteria evidence, not confidence language.
A revenue number is an output, not a wish. It is produced by capacity times productivity times coverage, steered by comp, and enforced by clean stage data. If you cannot decompose a target into those inputs, you do not have a plan, you have a hope with a deadline. A dashboard tells you coverage is 2.1x. An audit tells you which leads got dropped. RevOps sets the coverage target, sizes the capacity to hit it, designs the quota and comp that make the number reachable, and inspects the forecast so the number you commit is the number you land. The other skills report on the system. This one runs it.
Jobs to Be Done
| Job | Trigger | Output |
|---|---|---|
| Funnel Definitions | Stages or hand-off criteria disputed | One written set of stages with buyer-action exit criteria |
| Coverage and Capacity | Target set, or "can we hit it?" | Reps needed, quota, coverage, ramp-adjusted, opps to source |
| Territory and Quota | New year, new hires, unbalanced patches | Territories balanced on potential, quota reconciled top-down and bottom-up |
| Comp Plan | New role, wrong behavior, churn problem | Pay mix, commission rate, accelerators, clawbacks, aligned to the motion |
| Forecast Call | Weekly cadence, board number | Inspected commit and best-case, forecast accuracy tracked |
| Deal Desk | Non-standard price, term, or discount | Approval ruling against thresholds, discount governed |
| Funnel Hygiene | Numbers do not add up, forecast misses | Stage conversion, velocity, leakage, and the data fix |
What ships with it
10 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.
- evals/01_capacity_and_coverage_plan.json 1.7 KB
- evals/02_forecast_call_inspection.json 1.7 KB
- evals/03_comp_plan_for_the_motion.json 1.5 KB
- evals/04_planted_defect_forecast_inflation.json 1.5 KB
- references/comp_plan_design.md 6.6 KB
- references/deal_desk_and_discounting.md 5.2 KB
- references/forecast_call_methodology.md 6.2 KB
- references/funnel_definitions.md 7.2 KB
- references/pipeline_hygiene_metrics.md 5.6 KB
- references/quota_and_capacity.md 7.7 KB
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.
- 4d ago First seen · 101 lines · 71 tokens per session scan A 720a2f409436
resonance-sales-revops is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 2d ago), licensed MIT. It adds 71 tokens to every session and 2,844 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
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
requirements-author
Requirements authoring guide for BRD and PRD across Discover, Define, and Govern with canonical templates and handoff contracts.
mps-aspect-actions
Use when defining or editing MPS node factories (the "actions" aspect) — NodeFactories roots, per-concept NodeFactory setup functions that initialize a freshly created node and optionally copy data from a replaced sampleNode, plus the actions aspect's CopyPasteHandlers and PasteWrappers roots. Reach for this skill…
devtools-event-client
Create typed EventClient for a library. Define event maps with typed payloads, pluginId auto-prepend namespacing, emit()/on()/onAll()/onAllPluginEvents() API. Connection lifecycle (5 retries, 300ms), event queuing, enabled/disabled state, SSR fallbacks, singleton pattern. Unique pluginId requirement to avoid event…
api-design
REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.
crypto-market-rank
Crypto market rankings and leaderboards. Query trending tokens, top searched tokens, Binance Alpha tokens, tokenized stocks, social hype sentiment ranks, smart money inflow token rankings, top meme token rankings from Pulse launchpad, and top trader PnL leaderboards. Use this skill when users ask about token rankings…