claude-code-orchestra: Skill for Claude Code

.claude/skills/spike/SKILL.md

spike is a skill for Claude Code from DeL-TaiseiOzaki/claude-code-orchestra. It costs 141 tokens per session (6,364 once invoked), scanned A, original, MIT.

A time-limited technical investigation that examines whether an idea, technology, or design is feasible. It produces a go/no-go decision document, not an implementation plan.

In plain words
What is it for?
Use it to evaluate technologies, libraries, architecture choices, performance assumptions, or migration risks. After a go decision, a separate planning and implementation process is used.
Why use it?
It helps answer uncertain technical questions before work is committed to building something. The investigation gathers evidence and identifies constraints and risks.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions subagents; runs codex exec.

This is DeL-TaiseiOzaki/claude-code-orchestra's own configuration. It tells Claude Code how to work on claude-code-orchestra itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-code-orchestra configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 .claude/skills/_shared/workspace.py --skill spike --title "{short English title}" --create.

Reuse

Borrowing it

Nothing to install: this file belongs to DeL-TaiseiOzaki/claude-code-orchestra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/DeL-TaiseiOzaki/claude-code-orchestra/main/.claude/skills/spike/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/DeL-TaiseiOzaki/claude-code-orchestra

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/del-taiseiozaki/claude-code-orchestra/spike/github.svg)](https://agentmods.dev/skills/del-taiseiozaki/claude-code-orchestra/spike)
Your own site
<a href="https://agentmods.dev/skills/del-taiseiozaki/claude-code-orchestra/spike"><img src="https://agentmods.dev/badge/skills/del-taiseiozaki/claude-code-orchestra/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/del-taiseiozaki/claude-code-orchestra/spike"><img src="https://agentmods.dev/badge/skills/del-taiseiozaki/claude-code-orchestra/spike.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 141 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,364 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Agent Snooping · line 339
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
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.00141 $0.06364
Opus 5.5 $0.00056 $0.02546
Sonnet 5.5 $0.00028 $0.01273
Haiku 4.5 $0.00014 $0.00636

Measured 1mo ago against content hash 2524bb872718, 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 1mo 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.

.claude/skills/spike/SKILL.md · 579 lines

How it starts

The opening of the file, as written. The whole thing — 579 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spike

Codex-first time-boxed technical investigation skill leveraging Codex deep reasoning, Opus 1M context, and Agent Teams.

Preflight: ensure codex CLI is current (see codex-system skill).

Overview

This skill handles time-boxed feasibility studies and technical investigations. It produces a decision document (go/no-go recommendation), NOT an implementation plan. After a GO decision, the user proceeds to /feature (existing or greenfield mode) for actual implementation.

/spike <question or hypothesis>    <- This skill (investigation & decision)
    | After GO decision
/feature                            <- Implementation planning
    | After approval
/team-execute                      <- Parallel implementation + review

When to Use

Situation Example
Technology feasibility "Can we use WebSocket for real-time sync?"
Library evaluation "Is DuckDB suitable for our analytics pipeline?"
Architecture question "Should we use event sourcing for the order system?"
Performance hypothesis "Can we serve 10k concurrent requests with this stack?"
Migration risk "What would it take to migrate from REST to gRPC?"
Integration question "Can we integrate with the Stripe Connect API for our use case?"

When NOT to Use

  • Bug diagnosis → /troubleshoot
  • Known feature to implement → /feature
  • Simple library lookup → direct research (Opus subagent)
  • Code review → /team-execute --review-only

Full skill routing: AGENTS.md section "Routing Policy".

Investigation Modes

Mode Description When to Use
RESEARCH-ONLY No code written. Pure analysis from docs, examples, and Codex reasoning. Library evaluation, architecture questions, migration risk
PROTOTYPE Small throwaway code to validate a specific technical question. Code is NOT production-quality. Performance hypothesis, API integration feasibility, compatibility testing

Read the full file on GitHub · 579 lines

Files

What ships with it

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

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. 1mo ago Changed 2524bb872718
  2. 2mo ago Changed e4674ebfc33a
  3. 2mo ago First seen · 579 lines · 141 tokens per session scan A 774743d48132

Subscribe to this mod's changes

spike is a skill published in the GitHub repository DeL-TaiseiOzaki/claude-code-orchestra (198 stars, last pushed 5d ago), licensed MIT. It adds 141 tokens to every session and 6,364 once invoked, about $0.0006 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-30.

Related

spike compared with skills from other repositories

spike next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
spikeDeL-TaiseiOzaki/claude-code-orchestraSkill1985d agoMITA141Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code