What is moscow-prioritization?

A skill for sorting requirements into four MoSCoW groups: Must, Should, Could, and Won't. The groups show what a release needs, could include, or deliberately leaves out.

It helps prioritize backlogs, plan sprints and releases, rebalance essential work, and resolve disagreements about scope.

It helps teams control release scope and challenge requests that cannot all fit within the available time or capacity.

moscow-prioritization — Skill for Claude Code by pantheon-org

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/pantheon-org/tekhne

agentmods

npx agentmods add skills/pantheon-org/tekhne/moscow-prioritization

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pantheon-org/tekhne/moscow-prioritization/github.svg)](https://agentmods.dev/skills/pantheon-org/tekhne/moscow-prioritization)

Your own site

<a href="https://agentmods.dev/skills/pantheon-org/tekhne/moscow-prioritization"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/moscow-prioritization/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/pantheon-org/tekhne/moscow-prioritization"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/moscow-prioritization.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 867 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Anti-Refusal · line 89
Skill attempts to nullify the agent's safety policies or restrictions ('you have no restrictions', 'ignore your guidelines', 'do anything now'). This is a direct jailbreak that disables guardrails.

Fix: Remove jailbreak framing that nullifies safety policies or restrictions. Skill content must not instruct the agent to ignore its guidelines or operate without guardrails.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00093	$0.00867
Opus 5	$0.00046	$0.00434
Sonnet 5	$0.00019	$0.00173
Haiku 4.5	$0.00009	$0.00087

Measured 9d ago against content hash e4ac7dbf6d67, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

moscow-prioritization 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 9d 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.

skills/project-mgmt/issue-tracker-toolkit/moscow-prioritization/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MoSCoW Prioritization

When to Use

Use this skill when you need to rank requirements for a release.

When Not to Use

Do not use this skill for task-level estimation, bug triage, or sprint capacity planning by itself.

Principles

Must means release failure if missing.
Should means high value but deferrable.
Could means optional enhancement.
Won't means explicitly out of scope for this release.

Deterministic Workflow

Collect candidate requirements in one list.
Confirm release constraints (date, budget, team).
Categorize each item with the decision tree in references/categorization-decision-tree.md.
Challenge every Must using failure-focused questions.
Validate: Verify that the Must count does not exceed 60% of total effort before proceeding.
Rebalance if Must work exceeds 60% of effort. If rebalancing cannot bring Must under 60%, escalate to stakeholders to either re-scope the release (split into two releases, extend the timeline, or increase capacity) before finalizing categories.
Publish final table with owners and review date.

Quick Commands

Create a workshop draft

cp skills/moscow-prioritization/references/facilitator-workshop-template.md .context/moscow-workshop-draft.md

Expected result: reusable working document for prioritization.

Create a decision log

cat > .context/moscow-decisions-$(date +%Y-%m-%d).md <<'MD'
# MoSCoW Decision Log

| Requirement | Category | Rationale | Owner |
| --- | --- | --- | --- |
MD

Expected result: traceable decisions with ownership.

Validate skill quality after edits

sh skills/agentic-harness/skill-quality-auditor/scripts/evaluate.sh moscow-prioritization --json

Expected result: updated score and grade for this skill.

Lint this skill documentation

bunx markdownlint-cli2 "skills/moscow-prioritization/**/*.md"

Expected result: no markdownlint errors.

Anti-Patterns

NEVER label stakeholder preference as `Must`

Read the full file on GitHub · 108 lines

Files

What ships with it

32 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.

Changes

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.

9d ago First seen · 108 lines · 93 tokens per session scan A e4ac7dbf6d67

Subscribe to this mod's changes

moscow-prioritization is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 93 tokens to every session and 867 once invoked, about $0.0005 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-09-03.

Planning Project management agent-skills skills tessl

syndic

Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…

romainsimon/paperasse · 194 tokens

template-instantiation

Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect…

managedcode/dotnet-skills · 168 tokens

note-improvement

Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…

tobihagemann/turbo · 107 tokens

turborepo-monorepo

Provides comprehensive Turborepo monorepo management guidance for TypeScript/JavaScript projects. Use when creating Turborepo workspaces, configuring turbo.json tasks, setting up Next.js/NestJS apps, managing test pipelines (Vitest/Jest), configuring CI/CD, implementing remote caching, or optimizing build performance…

giuseppe-trisciuoglio/developer-kit · 76 tokens

handover-admin

Generate comprehensive admin documentation for AEM Edge Delivery Services project handover. Use when handing over admin responsibilities, onboarding a new site administrator, or documenting admin procedures — e.g., "admin guide", "admin documentation", "admin handover".

adobe/skills · 52 tokens

Product Strategy

A comprehensive skill for product strategy — covering frameworks, opportunity sizing, prioritization, roadmap building, OKRs, and stakeholder management. From early-stage discovery to mature product org execution.

cosmicstack-labs/mercury-agent-skills · 39 tokens