spike-wrap-up

spike-wrap-up is a skill for Claude Code, Codex from open-gsd/gsd-pi. It costs 102 tokens per session (1,662 once invoked), scanned A, original, MIT.

A project skill that turns the findings from a completed technical experiment, called a spike, into a reusable project-specific instruction file. It checks whether the result is worth preserving before writing it.

In plain words
What is it for?
Use it after a spike to interview the user about what should be reused and create a local skill for similar future work.
Why use it?
It prevents useful decisions and lessons from being lost when the experiment ends, while avoiding reusable guidance that does not apply.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions Claude Code.

Good fit Use it after a spike to interview the user about what should be reused and create a local skill for similar future work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/open-gsd/gsd-pi/spike-wrap-up
About the project

GSD Pi is a command-line coding agent and project workflow system that plans, implements, verifies, and tracks software work through milestones, tasks, Git worktrees, and stored project notes. It is for developers who want structured, longer-running agent sessions using different model providers. The catalogue entries extend GSD Pi with skills and agents.

open-gsd/gsd-pi · 1,214 stars · on GitHub · opengsd.net

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 open-gsd/gsd-pi --skill spike-wrap-up
Clone the repo
git clone --depth 1 https://github.com/open-gsd/gsd-pi

Made for: Claude Code, Codex.

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-wrap-up

README.md
[![agentmods](https://agentmods.dev/badge/skills/open-gsd/gsd-pi/spike-wrap-up/github.svg)](https://agentmods.dev/skills/open-gsd/gsd-pi/spike-wrap-up)
Your own site
<a href="https://agentmods.dev/skills/open-gsd/gsd-pi/spike-wrap-up"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-pi/spike-wrap-up/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-wrap-up

Your own site · 80×15
<a href="https://agentmods.dev/skills/open-gsd/gsd-pi/spike-wrap-up"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-pi/spike-wrap-up.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,662 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: 2 findings, 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 Rogue Agent · line 24
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
  • medium Agent Snooping · line 68
    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.00102 $0.01662
Opus 5 $0.00051 $0.00831
Sonnet 5 $0.00020 $0.00332
Haiku 4.5 $0.00010 $0.00166

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

Security

Grade A, and why

spike-wrap-up 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 6d 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.

src/resources/skills/spike-wrap-up/SKILL.md · 139 lines

How it starts

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

GSD already watches .agents/skills/ (and .claude/skills/ as a legacy compat path) at both user and project levels — see src/resources/extensions/gsd/skill-discovery.ts. Any skill written there is picked up on the next session without further wiring. This skill is the bridge from "spike done" to "skill available."

Invocation points:

  • End of Phase 3 (synthesize) in /gsd start spike — prompt suggests running this skill
  • User has a spike directory and wants to harvest it
  • Pre-existing RECOMMENDATION.md that deserves a permanent home

<core_principle> NOT EVERY SPIKE DESERVES A SKILL. If the recommendation was "don't do X," there may be no reusable guidance. Ask the user first; exit without writing if the answer is no.

PROJECT-LOCAL, NOT USER-GLOBAL. Write to .agents/skills/ in the project root, not ~/.agents/skills/. The skill encodes project-specific choices that should not leak into unrelated projects.

DESCRIPTION IS THE DISCOVERABILITY SIGNAL. The description field in frontmatter is the primary signal the agent uses to judge relevance and decide whether to load the skill — it is a heuristic, not a deterministic trigger. Write it as keywords the future agent will plausibly encounter, not a summary. </core_principle>

Step 1: Find the spike

  1. List directories under .gsd/workflows/spikes/ — sort by mtime, newest first.
  2. If multiple exist, ask the user which to wrap up. Default: the most recent.
  3. If none exist, tell the user and stop. This skill requires a completed spike.

Read the core files:

  • <spike>/SCOPE.md — the question that was asked
  • <spike>/research/*.md — the angles investigated
  • <spike>/RECOMMENDATION.md — the conclusion

Read the full file on GitHub · 139 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. 6d ago First seen · 139 lines · 102 tokens per session scan A 9b4bc8b0dcb5

Subscribe to this mod's changes

spike-wrap-up is a skill published in the GitHub repository open-gsd/gsd-pi (1,214 stars, last pushed today), licensed MIT. It adds 102 tokens to every session and 1,662 once invoked, about $0.0005 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-09-03.