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.
git clone --depth 1 https://github.com/ds1/boilerplate.mdWrote 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/ds1/boilerplate.md/probe-start)<a href="https://agentmods.dev/commands/ds1/boilerplate.md/probe-start"><img src="https://agentmods.dev/badge/commands/ds1/boilerplate.md/probe-start/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/ds1/boilerplate.md/probe-start"><img src="https://agentmods.dev/badge/commands/ds1/boilerplate.md/probe-start.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.00000 | $0.00892 |
| Opus 5.5 | $0.00000 | $0.00357 |
| Sonnet 5.5 | $0.00000 | $0.00178 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
probe-start 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Probe: Full Socratic Analysis
Launch 6 parallel Socratic evaluation agents to analyze a document, then synthesize findings.
Usage
/probe-start <path-to-document> <output-directory>
Arguments
$ARGUMENTS- Path to document to analyze and output directory (space-separated)
Prompt
You are orchestrating a comprehensive Socratic analysis. Parse the arguments to get:
- The document path (first argument)
- The output directory (second argument)
Step 1: Launch 6 Parallel Analysis Agents
Use the Task tool to launch 6 subagents in parallel. Each agent should:
- Read the source document
- Apply their specialized Socratic questioning technique
- Write their evaluation as a markdown file to the output directory
Agent 1: Clarify Thinking -> socratic-1-clarify-thinking.md
Examine arguments by asking: "What do you mean by...?", "What is the source of this idea?", "How did you come to this conclusion?"
- Identify key claims needing clarification
- Question definitions and terminology
- Trace origin of conclusions (primary research vs. inference)
- Examine reasoning chains
- Highlight ambiguities
Agent 2: Challenge Assumptions -> socratic-2-challenge-assumptions.md
Ask: "What are you assuming here?", "How do you know this is true?", "What if you were wrong?"
- Identify hidden assumptions
- Question foundational premises
- Challenge comparison methodology
- Test robustness of conclusions
Agent 3: Evidence Basis -> socratic-3-evidence-basis.md
Ask: "What evidence supports this?", "Is this evidence sufficient?", "What would disprove this?"
- Audit sources for bias and reliability
- Identify unsupported assertions
- Evaluate evidence quality for key claims
- Assess completeness of evidence
Agent 4: Alternative Viewpoints -> socratic-4-alternative-viewpoints.md
Ask: "What is the counter-argument?", "Who would disagree?", "What are other ways to look at this?"
- Present strongest counter-arguments
- Identify unrepresented stakeholder perspectives
- Explore internal contradictions
- Steel-man rejected options
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 · 100 lines · 0 tokens per session scan A 9e071a89eaeb
probe-start is a command published in the GitHub repository ds1/boilerplate.md (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 892 tokens. 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.
probe-start compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| probe-startds1/boilerplate.md | Command | 5 | 8mo ago | MIT | A | 0 | Claude Code |
| atomic-plandamusix/atomic-claude | Command | 115 | 5d ago | MIT | A | 54 | Claude Code |
| review-branchdamusix/atomic-claude | Command | 115 | 5d ago | MIT | A | 35 | Claude Code |
| spreadsheet-auditintellegix/intellegix-code-agent-toolkit | Command | 57 | 4d ago | MIT | A | 0 | Claude Code |
| session-reportdamusix/atomic-claude | Command | 115 | 5d ago | MIT | A | 31 | Claude Code |
| safe-buildryo-ebata/cc-audit | Command | 26 | yesterday | MIT | A | 0 | Claude Code |
| create-task-list.templateevan043/claude-cli-advanced-starter-pack | Command | 61 | 3mo ago | MIT | A | 0 | Claude Code |