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 MotWakorb/ai-agent-dev-team --skill spikegit clone --depth 1 https://github.com/MotWakorb/ai-agent-dev-teamWrote 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/motwakorb/ai-agent-dev-team/spike)<a href="https://agentmods.dev/skills/motwakorb/ai-agent-dev-team/spike"><img src="https://agentmods.dev/badge/skills/motwakorb/ai-agent-dev-team/spike.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.00039 | $0.02013 |
| Opus 5 | $0.00019 | $0.01007 |
| Sonnet 5 | $0.00008 | $0.00403 |
| Haiku 4.5 | $0.00004 | $0.00201 |
Grade A, and why
spike 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.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Spike
A spike answers a specific question that's blocking a decision. It is not a planning session, not a review, not a free-form exploration. One question in, findings out.
Preflight: Verify Onboarding & Effective Tier
Before any other step, verify deployment-tier setup. A spike that recommends an enterprise-tier solution for a home-lab problem is wasted compute.
-
Check
COMPONENTS.mdexists at the repo root. If missing, refuse to run and tell the PO:This project hasn't been onboarded yet. Run
/onboardfirst — it producesCOMPONENTS.md, which records each component's deployment tier. Spikes need this to scope investigation appropriately. See_shared/deployment-tier.mdfor the tier model.Do not proceed.
-
Identify the in-scope component(s) the spike question is about. If the question doesn't make this obvious, ask the PO.
-
Look up tiers in
COMPONENTS.md. If the in-scope component is missing, ask the PO to add it (with reasoning) before proceeding. -
Resolve cross-tier conflicts using strictest-wins by default.
-
Inject tier context into every agent prompt. Every prompt below must additionally include:
Read ~/.claude/skills/_shared/deployment-tier.md. In-scope components and tiers: [component] ([tier]), ... Effective tier for this spike: [tier] Investigate at the effective tier. Do not recommend enterprise-tier solutions for a home-lab problem. If the answer to the question changes by tier, present both — but anchor your recommendation at the effective tier.
Model Selection
When spawning agents, pass model: explicitly per _shared/orchestration.md (Agent Model Selection). For this skill:
- Lead persona for the spike question:
opus— investigation depth is the deliverable - Supporting personas:
sonnet
Tier modulation: at home-lab effective tier, downshift one level except security-engineer.
Process
Step 1: Define the Spike
Every spike has exactly three things:
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 · 171 lines · 39 tokens per session scan A 2522e3334a94
spike is a skill published in the GitHub repository MotWakorb/ai-agent-dev-team (2 stars, last pushed 25d ago), licensed MIT. It adds 39 tokens to every session and 2,013 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 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…