Borrowing it
Nothing to install: this file belongs to heznpc/PLOIDY. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/heznpc/PLOIDY/main/.claude/commands/spike.mdgit clone --depth 1 https://github.com/heznpc/PLOIDYWrote 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/commands/heznpc/ploidy/spike)<a href="https://agentmods.dev/commands/heznpc/ploidy/spike"><img src="https://agentmods.dev/badge/commands/heznpc/ploidy/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.
<a href="https://agentmods.dev/commands/heznpc/ploidy/spike"><img src="https://agentmods.dev/badge/commands/heznpc/ploidy/spike.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.00821 |
| Opus 5.5 | $0.00014 | $0.00328 |
| Sonnet 5.5 | $0.00007 | $0.00164 |
| Haiku 4.5 | $0.00004 | $0.00082 |
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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The user is asking for a pre-implementation gut check on the following idea:
$ARGUMENTS
You hold full project context (repo layout, prior decisions, constraints). That context is exactly what biases you — Ploidy's paper shows that Deep sessions rationalise ideas that fit the existing system even when they are objectively weak. Run the four-step spike without asking the user to confirm.
1 · Write the Deep-context take
In ~200 words, answer these in order:
- Fit — does this idea slot cleanly into the existing architecture? Name the concrete touch points.
- Implementation risks — what will actually break or be annoying? Be specific (files, components, tests, deploy paths).
- Honesty check — what piece of your support for this idea is because it's convenient to build rather than correct? If none, say so explicitly.
Tag every risk / concern HIGH / MEDIUM / LOW. Do not hedge.
2 · Spawn a Fresh sub-agent
Use the Agent tool (subagent_type="general-purpose"). It must see only
the idea, not the repo.
Prompt the subagent with exactly:
You have no background about any existing system. Evaluate this idea on its own merits: $ARGUMENTS
Cover in under 200 words:
- What problem does this solve? State it in your own words — if you can't, say "unclear".
- What assumptions does the idea rely on?
- What would make this a bad idea, assuming nothing about the existing stack?
Do not ask for more context. Do not request a repo link.
Capture the subagent's reply as the fresh position.
3 · Converge via Ploidy
Call the debate MCP tool:
debate(
prompt=$ARGUMENTS,
mode="solo",
deep_position=<your step-1 text>,
fresh_position=<subagent's step-2 text>,
deep_label="Project-context",
fresh_label="First-principles",
)
Add a deep_challenge if you found Fresh missing a project-specific
constraint. Add a fresh_challenge if Fresh surfaced an assumption you
were glossing over. Both optional.
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.
- 2mo ago First seen · 96 lines · 36 tokens per session scan A 1ce89669bf1c
spike is a command published in the GitHub repository heznpc/PLOIDY (0 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 821 once invoked, about $0.0001 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.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.