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 neurofoo/agent-skills --skill moscowgit clone --depth 1 https://github.com/neurofoo/agent-skillsWrote 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/neurofoo/agent-skills/moscow)<a href="https://agentmods.dev/skills/neurofoo/agent-skills/moscow"><img src="https://agentmods.dev/badge/skills/neurofoo/agent-skills/moscow.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.00043 | $0.00558 |
| Opus 5 | $0.00022 | $0.00279 |
| Sonnet 5 | $0.00009 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
moscow 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.
What it actually says
MoSCoW Prioritization
Categorize items into Must have, Should have, Could have, and Won't have for clear scope and priorities.
Instructions
Take the list of items provided and sort them into MoSCoW categories. Be rigorous about what's truly a "Must"—if the project/goal can still succeed without it, it's not a Must.
Output Format
Context What are we prioritizing for? What are the constraints (time, budget, capacity)?
Prioritized List
Must Have (Critical)
Without these, the project fails or is pointless
- [Item] — [Why it's a must]
- [Item] — [Why it's a must]
Should Have (Important)
Significantly adds value; painful to omit but project survives
- [Item] — [Value it adds]
- [Item] — [Value it adds]
Could Have (Nice to Have)
Desirable if time permits; low impact if cut
- [Item] — [Why it's optional]
- [Item] — [Why it's optional]
Won't Have (Not This Time)
Explicitly out of scope; may revisit later
- [Item] — [Why it's deferred]
- [Item] — [Why it's deferred]
Effort Distribution
| Category | Items | Est. Effort % |
|---|---|---|
| Must | X | ≤60% |
| Should | X | ~20% |
| Could | X | ~10% |
| Won't | X | 0% (deferred) |
Red Flags
- If Must > 60% of effort: scope may be too large
- If no Won'ts: probably not being honest about constraints
- If everything is Must: priorities haven't been set
Rationale Explain the key trade-offs made and the reasoning behind contentious categorizations.
Next Step What's the first Must item to tackle?
Guidelines
- Ask "If we shipped without this, would we fail?" for each Must
- Challenge "Musts" that are really "someone really wants this"
- Make Won'ts explicit—avoids scope creep later
- Consider dependencies (a Must might require a "hidden" Must)
- Stakeholder alignment is essential—this isn't just your opinion
$ARGUMENTS
What ships with it
2 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 · 75 lines · 43 tokens per session scan A 033c03e7d7d2
moscow is a skill published in the GitHub repository neurofoo/agent-skills (111 stars, last pushed 7mo ago), licensed MIT. It adds 43 tokens to every session and 558 once invoked, about $0.0002 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…