What is tp-spike-results?

A command that records what a completed or partly completed spike discovered. It creates a structured results document covering findings, demos, and architecture decisions.

Use it after experimentation to document observations, created demonstrations, and the verdict about what approach to take.

It preserves the evidence and reasoning from an experiment so its outcome can guide later implementation or design decisions.

tp-spike-results — Skill for Claude Code by CurtisThe

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 CurtisThe/three-pillars-plugin --skill tp-spike-results

Clone the repo

git clone --depth 1 https://github.com/CurtisThe/three-pillars-plugin

Made for: Claude Code.

Or install three-pillars, the plugin that ships this one along with the rest of its 37 skills, 20 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/curtisthe/three-pillars-plugin/tp-spike-results/github.svg)](https://agentmods.dev/skills/curtisthe/three-pillars-plugin/tp-spike-results)

Your own site

<a href="https://agentmods.dev/skills/curtisthe/three-pillars-plugin/tp-spike-results"><img src="https://agentmods.dev/badge/skills/curtisthe/three-pillars-plugin/tp-spike-results/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/curtisthe/three-pillars-plugin/tp-spike-results"><img src="https://agentmods.dev/badge/skills/curtisthe/three-pillars-plugin/tp-spike-results.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,430 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.

Model	Per session	Once invoked
Fable 5.1	$0.00036	$0.01430
Opus 5	$0.00018	$0.00715
Sonnet 5	$0.00007	$0.00286
Haiku 4.5	$0.00004	$0.00143

Measured 9d ago against content hash cd0fccbd88f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

tp-spike-results 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 9d 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.

skills/tp-spike-results/SKILL.md · 89 lines

How it starts

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

Spike Results

Capture the findings from a completed or partially completed spike into a structured results document.

Arguments:

{spike-name} (required) — must match an existing directory under three-pillars-docs/tp-designs/.
--auto (optional) — autonomous mode. Derives findings from artifacts instead of interviewing user, logs verdict reasoning to decisions.md. See skills/_shared/auto-mode.md for convention.

Prerequisites

three-pillars-docs/tp-designs/{spike-name}/design.md must exist.
Some experimentation must have been done (code written, demos rendered, or observations made).

Steps

Run first-run preflight per skills/_shared/first-run.md.
Validate {spike-name}: must match [a-z0-9-]+. Reject values containing /, .., spaces, or characters outside [a-z0-9-].
Run collaboration preflight per skills/_shared/collaboration.md with phase: "spike-results". The spike-results artifact is the verdict record — it must be written by the rightful owner. Honor --force-takeover if passed. In --auto mode, do not prompt — if the lock is held by another developer, log the conflict to decisions.md and stop.
Read all artifacts in the spike directory: design.md, plan.md (if exists), any code files, and note any demo files (MP4s, screenshots, logs).
Capture findings:
- Normal mode: Have a conversation with the user:
  - What worked? What didn't? What surprised you?
  - What's the verdict — GO, PARTIAL, or NO-GO?
  - What reusable patterns or primitives were discovered?
  - What architecture decisions emerged?
  - Which downstream designs are affected?
- --auto mode: Derive findings autonomously from available artifacts:
  - Read plan.md task statuses (Done/Blocked/Abandoned) to assess what worked and what didn't.
  - Read decisions.md for the full history of choices, simplifications, and boundary assessments.
  - Scan code changes (git diff from spike start) for patterns and primitives.
  - Assess verdict against design.md success criteria — map task outcomes to GO/PARTIAL/NO-GO thresholds.
  - Log verdict reasoning to decisions.md with confidence level.
Write three-pillars-docs/tp-designs/{spike-name}/spike-results.md with this structure:

Read the full file on GitHub · 89 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.

9d ago First seen · 89 lines · 36 tokens per session scan A cd0fccbd88f7

Subscribe to this mod's changes

tp-spike-results is a skill published in the GitHub repository CurtisThe/three-pillars-plugin (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 1,430 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.

Planning Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens