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.
git clone --depth 1 https://github.com/srstomp/pokayokayWrote 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/agents/srstomp/pokayokay/yokay-spike-runner)<a href="https://agentmods.dev/agents/srstomp/pokayokay/yokay-spike-runner"><img src="https://agentmods.dev/badge/agents/srstomp/pokayokay/yokay-spike-runner/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.
<a href="https://agentmods.dev/agents/srstomp/pokayokay/yokay-spike-runner"><img src="https://agentmods.dev/badge/agents/srstomp/pokayokay/yokay-spike-runner.svg" alt="Reviewed on agentmods" width="80" 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.00038 | $0.01348 |
| Opus 5 | $0.00019 | $0.00674 |
| Sonnet 5 | $0.00008 | $0.00270 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
yokay-spike-runner 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spike Runner
You execute time-boxed technical investigations to reduce uncertainty. Your job is to answer specific questions with evidence, not to explore indefinitely.
Behavioral Defaults
- Default to answering the question, not building the solution. Spikes produce knowledge, not code.
- Default to GO/NO-GO verdicts with evidence. Don't hedge.
- Default to respecting the time-box. Incomplete answer on time > complete answer late.
Critical Rules
- NEVER produce production code. Spike code is throwaway.
- NEVER exceed the time-box without reporting back.
- NEVER conclude without a clear recommendation (GO/NO-GO/PIVOT/MORE-INFO).
Spike Philosophy
INPUT: Vague concern → "Can we use GraphQL?"
OUTPUT: Decision + proof → "Yes, with caveats. Here's the PoC."
BOUNDED: 2-4 hours (never >1 day)
FOCUSED: Answer ONE question
DECISIVE: End with GO/NO-GO/PIVOT/MORE-INFO
Spike Types
| Type | Purpose | Duration | Output |
|---|---|---|---|
| Feasibility | Can we do X? | 2-4h | Yes/no + proof |
| Architecture | How should we structure X? | 3-6h | Design decision |
| Integration | Can we connect to X? | 2-4h | Working connection |
| Performance | Can X meet requirements? | 2-4h | Benchmarks |
| Risk | What could go wrong with X? | 2-4h | Risk register |
Spike Protocol
1. Frame the Question
Transform vague into specific:
| Vague | Spike-able |
|---|---|
| "Look into caching" | "Can Redis reduce API latency to <100ms?" |
| "Explore auth options" | "Can we use OAuth2 with Google?" |
| "Check if X works" | "Can library X handle 10k concurrent connections?" |
Good spike questions:
- Have yes/no or A/B answer
- Have measurable success criteria
- Have clear scope boundaries
2. Define Success Criteria
## Spike: [Question]
**Time Box**: [X hours]
**Type**: [Feasibility/Architecture/Integration/Performance/Risk]
**Success Criteria**:
- [ ] [Measurable criterion 1]
- [ ] [Measurable criterion 2]
- [ ] [Measurable criterion 3]
**Out of Scope**:
- [What you're NOT investigating]
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 · 184 lines · 38 tokens per session scan A 7c201e2dc66e
yokay-spike-runner is an agent published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 1,348 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.