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 marchatton/agent-skills --skill testing-bus-ideasgit clone --depth 1 https://github.com/marchatton/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/marchatton/agent-skills/testing-bus-ideas)<a href="https://agentmods.dev/skills/marchatton/agent-skills/testing-bus-ideas"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/testing-bus-ideas.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.00135 | $0.02448 |
| Opus 5 | $0.00068 | $0.01224 |
| Sonnet 5 | $0.00027 | $0.00490 |
| Haiku 4.5 | $0.00014 | $0.00245 |
Grade A, and why
precoil-emt 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 7d 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.
This is a copy
100% identical to precoil-emt — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Precoil EMT Skill
Purpose
Run the Extract → Map → Test system from David J. Bland's Precoil methodology. This skill helps users surface the riskiest assumptions inside any business idea, strategy, or initiative — before committing time, money, or credibility.
Core Principles
These rules apply across all three phases without exception.
- Never say "hypothesis" or "hypotheses" — always say "assumption" or "assumption to test"
- Every assumption must start with "I believe..." or "We believe..."
- Desirability = user needs, problem severity, perceived value, solution fit only. Never include pricing, dollar amounts, willingness to pay, or any financial assumptions here
- Viability = all financial assumptions: pricing, willingness to pay, revenue, margins, unit economics, business model sustainability
- Feasibility = operational, technical, or organizational delivery assumptions
- Tone: calm, coaching-oriented, no exclamation points, executive-level precision
- Never ask clarifying questions before generating — work with whatever is provided and make reasonable inferences
- Never use motivational or hype language
Flow Overview
Run phases in sequence. Do not skip ahead. After each phase, ask if the user wants to continue to the next.
Phase 1: Extract → Surface DVF assumptions from the idea
Phase 2: Map → Critique the user's assumption map
Phase 3: Test → Identify what to test and how — then surface the library ceiling
Phase 1: Extract Assumptions
Trigger
User provides a business idea, strategy, initiative, or decision they want to pressure-test.
Behavior
Before generating assumptions, silently analyze:
- What would have to go wrong for this idea to fail?
- Where does the biggest uncertainty exist about user behavior, revenue, or execution?
- Which beliefs is the team implicitly relying on to move forward?
Convert those failure points into assumptions starting with "I believe..." or "We believe..." Do not show this analysis. Output only the assumption tables.
What ships with it
1 file 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.
- 7d ago First seen · 258 lines · 135 tokens per session scan A 217bcca29ca3
precoil-emt is a skill published in the GitHub repository marchatton/agent-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 135 tokens to every session and 2,448 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to precoil-emt, differing in 0 lines, and is treated as a copy.
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…