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/idoforgod/Dissertation-Simulator-AgenticWorkflowWrote 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/idoforgod/dissertation-simulator-agenticworkflow/thesis-start)<a href="https://agentmods.dev/commands/idoforgod/dissertation-simulator-agenticworkflow/thesis-start"><img src="https://agentmods.dev/badge/commands/idoforgod/dissertation-simulator-agenticworkflow/thesis-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/idoforgod/dissertation-simulator-agenticworkflow/thesis-start"><img src="https://agentmods.dev/badge/commands/idoforgod/dissertation-simulator-agenticworkflow/thesis-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.00022 | $0.00726 |
| Opus 5.5 | $0.00009 | $0.00290 |
| Sonnet 5.5 | $0.00004 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
thesis-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 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thesis Start / Continue
Resume or start the thesis workflow execution.
Protocol
Step 1: Read Current State
python3 "$CLAUDE_PROJECT_DIR"/.claude/hooks/scripts/checklist_manager.py \
--status \
--project-dir "$CLAUDE_PROJECT_DIR/thesis-output/{project}"
If no project exists, redirect to /thesis:init.
Step 2: Determine Next Action
Based on current_step and input_mode in SOT:
| Current Position | Action |
|---|---|
| Step 0 (fresh) | Begin Phase 0 initialization |
| Phase 0-A steps | Topic exploration with @topic-explorer |
| Phase 0-D steps | Learning mode with Agent Team |
| HITL-1 | Present research question candidates for user approval |
| Wave 1-5 steps | Literature review with Agent Teams |
| Gate steps | Run cross-validation gate |
| HITL-2+ | Present results for user review |
| Phase 2 steps | Research design with Agent Team |
| Phase 3 steps | Thesis writing with Agent Team |
| Phase 4 steps | Publication strategy |
Step 3: Get Invocation Plan
Query the P1-computed invocation plan to determine remaining orchestrator invocations:
python3 "$CLAUDE_PROJECT_DIR"/.claude/hooks/scripts/query_step.py \
--invocation-plan --step {current_step} --project-dir "$CLAUDE_PROJECT_DIR/thesis-output/{project}"
Where {current_step} is the value obtained from Step 1's SOT status.
This returns a list of invocation blocks (17 total), each with start, end, label, and status (pending/in_progress/completed). Use this to determine which invocations remain.
Step 4: Execute via Orchestrator Loop
For each pending or in_progress invocation block from the plan, invoke the thesis-orchestrator:
Agent: subagent_type="thesis-orchestrator", prompt="
Project directory: thesis-output/{project}
Current step: {current_step} (from SOT)
Invocation: {invocation_number}/{total_invocations} — {label}
Step range: {start}-{end}
Execution mode: {execution_mode}
Research topic: {research_question}
Execute steps {start} through {end} following your Execution Protocol.
Use step consolidation where query_step.py indicates (consolidate_with > 1 step).
Report back: completed steps, outputs created, any gate results.
"
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.
- 1mo ago First seen · 85 lines · 22 tokens per session scan A b5e9384c1b0d
thesis-start is a command published in the GitHub repository idoforgod/Dissertation-Simulator-AgenticWorkflow (108 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 726 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.