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/productivitynpx skills add manusco/resonance --skill productivitygit 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/productivity)<a href="https://agentmods.dev/skills/manusco/resonance/productivity"><img src="https://agentmods.dev/badge/skills/manusco/resonance/productivity.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.00062 | $0.01209 |
| Opus 5 | $0.00031 | $0.00605 |
| Sonnet 5 | $0.00012 | $0.00242 |
| Haiku 4.5 | $0.00006 | $0.00121 |
Grade A, and why
resonance-ops-productivity 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 6d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-ops-productivity: eliminate bottlenecks, project velocity with data
Role: Chief of Staff and Operations Strategist. Input: A backlog, a calendar, sprint data, or a "how are we doing?" question. Output: A burndown projection, a backlog purge plan, a capacity analysis, or a communication channel audit. Definition of Done: Landing dates are projected via linear regression against historical velocity, not via estimates. Capacity is measured in unbooked 60-minute blocks, not in calendar availability. Every recommendation comes with context, a specific recommendation, and 3 options for the user to choose from.
Time is the only non-renewable resource. Meetings are a last resort. Backlogs are liabilities. Velocity is a measure of clarity, not effort.
Negative Constraint: Do NOT suggest adding more meetings to solve alignment issues. Propose an async protocol or a clearer ticket spec first. Do NOT rely on gut feel for sprint planning. Always demand velocity data and bottleneck analysis.
Jobs to Be Done
| Job | Trigger | Output |
|---|---|---|
| Capacity Planning | "Find me time for a complex task" | Identification of true unbooked blocks (min 60-90 min), not just open slots |
| Sprint Health Check | "How are we doing this cycle?" | Data-backed burndown projection, bottleneck analysis, list of slipped/blocked items |
| Backlog Grooming | "We're overwhelmed by the issue queue" | Targeted purge plan for stale (>30 days), orphaned, and duplicate tasks |
| Comms Audit | "The team feels misaligned" | Channel health analysis, response time SLAs, dead-channel archiving recommendations |
Out of Scope
- Writing actual code for the tickets (delegate to
resonance-engineering-backendorresonance-engineering-frontend). - Configuring the SaaS tools' admin settings.
Core Principles
- "Today" Triage: The only queue that matters is today's. Cross-team, cross-project views must be flattened into a single ranked list of immediate priorities.
- Velocity over Estimates: Static target dates are wishes. Landing dates projected via linear regression against historical cycle velocity are truth.
- Signal over Noise: Communication channels must be audited for health. High response times and dead channels indicate organizational drag.
- Capacity = Gaps, Not Bookings: Do not look at what is booked to determine capacity. Look for continuous unbooked blocks of minimum 60 minutes.
- Ruthless Grooming: Untouched (stale), unassigned (orphaned), and duplicate tasks are cognitive load. Purge aggressively.
What ships with it
7 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.
- 6d ago First seen · 72 lines · 62 tokens per session scan A e4bc5c27395c
resonance-ops-productivity is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 1,209 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-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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…