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/tupe12334/instinct/moscownpx skills add tupe12334/instinct --skill moscowgit clone --depth 1 https://github.com/tupe12334/instinctWrote 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/tupe12334/instinct/moscow)<a href="https://agentmods.dev/skills/tupe12334/instinct/moscow"><img src="https://agentmods.dev/badge/skills/tupe12334/instinct/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 | $0.00024 | $0.01672 |
| Opus 5 | $0.00012 | $0.00836 |
| Sonnet 5 | $0.00005 | $0.00334 |
| Haiku 4.5 | $0.00002 | $0.00167 |
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 5d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MoSCoW Prioritization
Overview
MoSCoW sorts requirements or features into four buckets that define what ships in a given release. It forces explicit trade-off decisions before work starts, preventing scope creep and last-minute cuts.
┌────────────────────────────────────────────────────────────┐
│ M — Must Have │ Non-negotiable. Release fails without │
│ │ it. No workaround exists. │
├────────────────────────────────────────────────────────────┤
│ S — Should Have │ High value. Painful to omit but │
│ │ a workaround exists short-term. │
├────────────────────────────────────────────────────────────┤
│ C — Could Have │ Nice-to-have. Include only if time │
│ │ and budget allow. Drop first. │
├────────────────────────────────────────────────────────────┤
│ W — Won't Have │ Explicitly out of scope this cycle. │
│ │ Documented, not forgotten. │
└────────────────────────────────────────────────────────────┘
Category Definitions
Must Have
The minimum viable product for this release. If any Must is missing, the release must not ship. Apply the test: "Would a reasonable user/stakeholder refuse the release without this?" If yes — Must. Common examples: legal compliance, core user journey, safety-critical paths.
Should Have
Important requirements with a workaround. Users feel the absence but can cope temporarily. These typically ship in the next sprint or release. Common examples: search filters, email notifications, export to PDF.
Could Have
Desirable but low impact relative to effort. They're the first items cut when scope pressure hits. Common examples: UI polish, convenience shortcuts, non-default themes.
Won't Have (this time)
Explicitly de-scoped for this cycle. Writing it down prevents the item from re-entering scope informally or being assumed by stakeholders. It is not "rejected forever" — it is deferred and visible.
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.
- 5d ago First seen · 120 lines · 24 tokens per session scan A 908967c8fdf5
moscow is a skill published in the GitHub repository tupe12334/instinct (1 stars, last pushed 19d ago), licensed MIT. It adds 24 tokens to every session and 1,672 once invoked, about $0.0001 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-31.
Other skills, from other repositories
thinking-theory-of-constraints
When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.
thinking-lindy-effect
Use when longevity of a non-perishable option matters. Treat survival duration as a remaining-life prior, then check domain drift before favoring the proven.
thinking-kepner-tregoe
Use when a selective defect needs IS/IS-NOT difference analysis or a consequential option choice needs must/want weighting and adverse-consequence comparison.
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.