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 cwinvestments/memstack --skill scope-of-workgit clone --depth 1 https://github.com/cwinvestments/memstackWrote 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/cwinvestments/memstack/scope-of-work)<a href="https://agentmods.dev/skills/cwinvestments/memstack/scope-of-work"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/scope-of-work/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/cwinvestments/memstack/scope-of-work"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/scope-of-work.svg" alt="Reviewed on agentmods" width="80" 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.00070 | $0.03714 |
| Opus 5.5 | $0.00028 | $0.01486 |
| Sonnet 5.5 | $0.00014 | $0.00743 |
| Haiku 4.5 | $0.00007 | $0.00371 |
Grade A, and why
memstack-business-scope-of-work 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 1mo 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 — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📐 Scope of Work: Defining project boundaries and deliverables...
Generates a formal Scope of Work document with objectives, deliverables, acceptance criteria, in/out scope definitions, work breakdown structure, milestones, and change request process.
Activation
When this skill activates, output:
📐 Scope of Work, Defining project scope and deliverables...
Then execute the protocol below.
| Context | Status |
|---|---|
| User says "scope of work" or "SOW" or "define scope" | ACTIVE |
| User says "write SOW" or "project scope" or "scope document" | ACTIVE |
| Defining formal project boundaries for a client engagement | ACTIVE |
| Writing internal task lists (no formal scope needed) | DORMANT: use Work skill |
| Writing a proposal (includes pricing/sales) | DORMANT: use proposal-writer |
Anti-patterns
| Trap | Reality Check |
|---|---|
| "The scope is obvious from the proposal" | Proposals sell. SOWs define. Same project, different documents, different purpose. |
| "We don't need to list exclusions" | Every scope dispute starts with "I assumed it was included." List what's OUT explicitly. |
| "Acceptance criteria slow us down" | Acceptance criteria prevent "it's not what I wanted" after you've built it. They speed up delivery. |
| "We'll handle changes informally" | Informal changes create informal expectations. Formal change requests protect the timeline and budget. |
| "Dependencies don't matter yet" | Dependencies determine what blocks what. Discovering them mid-project causes delays. Map them upfront. |
Protocol
Step 1: Define Project Objectives
Establish what success looks like at the highest level:
## 1. Project Objectives
### Primary Objective
[One sentence: what this project delivers and why it matters]
Example: Build a multi-tenant SaaS dashboard that enables [Client]'s customers
to manage their accounts, view analytics, and configure integrations, replacing
the current manual process that requires 3 support staff.
### Success Criteria
| Criteria | Measurement | Target |
|----------|------------|--------|
| Core functionality | All deliverables pass acceptance criteria | 100% |
| Performance | Page load time under 3 seconds | p95 < 3s |
| Reliability | Uptime during business hours | 99.5% |
| User adoption | Active users within 30 days of launch | > 50% of target audience |
| Support reduction | Decrease in support tickets for covered workflows | > 40% reduction |
Success criteria must be **measurable**. "The client is happy" is not a success criterion.
"Support tickets decrease by 40%" is.
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.
- 1mo ago Changed bad42a8265b3
- 1mo ago First seen · 399 lines · 70 tokens per session scan A a9ec509480e1
memstack-business-scope-of-work is a skill published in the GitHub repository cwinvestments/memstack (425 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 3,714 once invoked, about $0.0003 per session on Opus 5.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
docs-canvas
Render a documentation-style OpenBitFun Canvas that organizes architecture notes, API references, walkthroughs, runbooks, and how-tos into a navigable layout with sections, tables of contents, diagrams, and cross-references. Use when the user asks for a docs canvas, documentation overview, architecture walkthrough…
investment-memo-generator
Investment memo creation combining financial analysis, document generation, and structured templates. Use when creating investment memos, pitch decks, deal summaries, or investment committee materials.
impact-report-writer
Nonprofit/NGO impact report generation with data visualization suggestions, outcome metrics, narrative structure, and program data presentation. Use when writing impact reports, annual reports, or program evaluation summaries.
codebase-documenter
Write codebase documentation: READMEs, architecture docs, getting-started guides, API docs, and code comments. Use when documenting code or making a project easier for new developers.
agent-documentation-writer
Specialist subagent: Generates comprehensive documentation including READMEs, API docs, architecture docs, and inline comments. Use when documenting code, creating guides, or explaining systems.
matplotlib-best-practices
Best practices for Matplotlib data visualization, plotting, and creating publication-quality figures in Python.