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/errc-gridnpx skills add tupe12334/instinct --skill errc-gridgit 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/errc-grid)<a href="https://agentmods.dev/skills/tupe12334/instinct/errc-grid"><img src="https://agentmods.dev/badge/skills/tupe12334/instinct/errc-grid.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.00026 | $0.02083 |
| Opus 5 | $0.00013 | $0.01042 |
| Sonnet 5 | $0.00005 | $0.00417 |
| Haiku 4.5 | $0.00003 | $0.00208 |
Grade A, and why
errc-grid 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 4d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ERRC Grid
Overview
The ERRC Grid is the core action tool of Blue Ocean Strategy (Kim & Mauborgne). It forces explicit decisions across four quadrants — Eliminate, Reduce, Raise, Create — to simultaneously cut costs and lift buyer value, rather than trading one off against the other. The output is a new value curve that diverges from the industry standard instead of benchmarking against it.
┌─────────────────────────────┬─────────────────────────────┐
│ ELIMINATE │ RAISE │
│ Factors the industry takes │ Factors to push well above │
│ for granted that add cost │ the industry standard │
│ but deliver no real value │ │
├─────────────────────────────┼─────────────────────────────┤
│ REDUCE │ CREATE │
│ Factors to drop below the │ Factors the industry has │
│ industry standard without │ never offered — new sources│
│ meaningfully hurting buyers│ of buyer value │
└─────────────────────────────┴─────────────────────────────┘
COST SIDE ◄──────────────────► VALUE SIDE
The Four Actions
Eliminate
Remove factors that incumbents compete on purely out of inertia. These are often costly to provide but buyers no longer value — or never valued in the first place. Elimination is the hardest action because it requires admitting that an industry practice is waste.
Reduce
Keep the factor but pull back to the minimum level that avoids buyer dissatisfaction. Use when a factor has real baseline value but the industry over-delivers on it, paying a cost premium buyers won't pay for in price.
Raise
Invest above the current industry ceiling on factors where buyers are underserved and willing to pay a premium. Raise only a small number of factors — raising everything is not a strategy, it is just spending more.
Create
Introduce factors that have never existed in this industry. These are the most defensible because competitors cannot copy what they have not yet conceived. Sources: look across substitute industries, buyer chains, or emotional vs functional appeal.
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.
- 4d ago First seen · 122 lines · 26 tokens per session scan A dba9aee91a84
errc-grid is a skill published in the GitHub repository tupe12334/instinct (1 stars, last pushed 19d ago), licensed MIT. It adds 26 tokens to every session and 2,083 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.