agentmods.dev

spike

spike is a skill for Claude Code from MotWakorb/ai-agent-dev-team. It costs 39 tokens per session (2,013 once invoked), scanned A, original, MIT.

A focused technical investigation for answering one question that is blocking an engineering decision. It checks the project's deployment setup and studies only the relevant people or components.

In plain words
What is it for?
Use it to investigate a specific technical unknown, verify the project is onboarded, identify the affected component, check its deployment tier, and return findings for a decision.
Why use it?
It prevents broad, unfocused research and avoids recommending solutions that do not fit the part of the system or deployment level being considered.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: reads .claude/ paths.

not rated 2repo 2mo ago A scan 39 tokens original MIT

Good fit Use it to investigate a specific technical unknown, verify the project is onboarded, identify the affected component, check its deployment tier, and return findings for a decision.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/motwakorb/ai-agent-dev-team/spike
View source ↗ MotWakorb/ai-agent-dev-team
Install

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.

Any agent
npx skills add MotWakorb/ai-agent-dev-team --skill spike
Clone the repo
git clone --depth 1 https://github.com/MotWakorb/ai-agent-dev-team

Made for: Claude Code.

Wrote 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.

agentmods badge for spike

README.md
[![agentmods](https://agentmods.dev/badge/skills/motwakorb/ai-agent-dev-team/spike/github.svg)](https://agentmods.dev/skills/motwakorb/ai-agent-dev-team/spike)
Your own site
<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/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.

agentmods 80×15 button for spike

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,013 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.02013
Opus 5.5 $0.00016 $0.00805
Sonnet 5.5 $0.00008 $0.00403
Haiku 4.5 $0.00004 $0.00201

Measured 2mo ago against content hash 2522e3334a94, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

spike/SKILL.md · 171 lines

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.

  1. Check COMPONENTS.md exists at the repo root. If missing, refuse to run and tell the PO:

    This project hasn't been onboarded yet. Run /onboard first — it produces COMPONENTS.md, which records each component's deployment tier. Spikes need this to scope investigation appropriately. See _shared/deployment-tier.md for the tier model.

    Do not proceed.

  2. Identify the in-scope component(s) the spike question is about. If the question doesn't make this obvious, ask the PO.

  3. Look up tiers in COMPONENTS.md. If the in-scope component is missing, ask the PO to add it (with reasoning) before proceeding.

  4. Resolve cross-tier conflicts using strictest-wins by default.

  5. 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:

Read the full file on GitHub · 171 lines

Changes

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.

  1. 2mo ago First seen · 171 lines · 39 tokens per session scan A 2522e3334a94

Subscribe to this mod's changes

spike is a skill published in the GitHub repository MotWakorb/ai-agent-dev-team (2 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 2,013 once invoked, about $0.0002 per session on Opus 5.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.

PlanningResearch
Related

spike compared with skills from other repositories

spike next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
spikeMotWakorb/ai-agent-dev-teamSkill22mo agoMITA39Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code