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.
npx agentmods add commands/bityoungjae/marketplace/continuegit clone --depth 1 https://github.com/BitYoungjae/marketplaceWrote 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/bityoungjae/marketplace/continue)<a href="https://agentmods.dev/commands/bityoungjae/marketplace/continue"><img src="https://agentmods.dev/badge/commands/bityoungjae/marketplace/continue.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.02448 |
| Opus 5 | $0.00017 | $0.01224 |
| Sonnet 5 | $0.00007 | $0.00490 |
| Haiku 4.5 | $0.00003 | $0.00245 |
Grade A, and why
continue 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 4d 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continue Session
Write the next N incomplete sections (default: 3).
Context Files
- Persona: @persona.md
- Project Context: @project-context.md
Current State
- Incomplete tasks: !
grep -c "\[ \]" task.md 2>/dev/null || echo "No task.md found"
Process
1. Parse Arguments
CRITICAL: Extract count, skip_review, and use_glm_tools flags from $ARGUMENTS.
skip_review = $ARGUMENTS.includes("--skip-review")
use_glm_tools = $ARGUMENTS.includes("--glm") ? "true" : "false"
count = parseInt($ARGUMENTS.replace("--skip-review", "").replace("--glm", "").trim()) || 3
The use_glm_tools value MUST be the string "true" or "false" for XML.
2. Read task.md and Extract Domain
Read task.md and identify all incomplete sections ([ ] items).
Read persona.md and extract domain information:
- Domain (from Domain Guidelines section header, e.g., "Domain Guidelines: Technology" → technology)
- If no Domain Guidelines section, default to "technology" for backward compatibility
Domain values: technology, history, science, arts, general
3. Build Section Queue
Create a queue of sections to write:
- Collect first
countincomplete ([ ]) items from task.md - Extract section IDs and titles for each queued item
3.5 Directory Resolution Helper
CRITICAL: Use multi-tier search to find existing research directories. This handles naming inconsistencies.
⚠️ Glob Returns Files Only
Glob does NOT return directories. All patterns MUST end with
/research.md.
Pattern Result .research/sections/*9-1*❌ Empty .research/sections/*9-1*/research.md✅ Works
Define a helper function to resolve research directories:
function resolveResearchDirectory(chapter, section, title):
# Normalize identifiers (from research-storage skill)
canonical_chapter = normalizeChapter(chapter)
# "1" → "01", "01" → "01", "10" → "10"
canonical_section = normalizeSection(section)
# "1" → "1", "01" → "1", "02" → "2"
canonical_slug = generateSlug(title)
# "Core Concepts" → "core-concepts"
# "What is React?" → "what-is-react"
canonical_path = ".research/sections/{canonical_chapter}-{canonical_section}-{canonical_slug}/"
# Tier 1: Exact canonical match
tier1 = Glob("{canonical_path}research.md")
if tier1 not empty:
return { path: canonical_path, existing: true, tier: 1 }
# Tier 2: Canonical chapter-section, any slug
tier2 = Glob(".research/sections/{canonical_chapter}-{canonical_section}-*/research.md")
if tier2 not empty:
return { path: parent(tier2[0]), existing: true, tier: 2 }
# Tier 3: Non-padded chapter variation
raw_chapter = String(parseInt(chapter, 10)) # "01" → "1"
tier3 = Glob(".research/sections/{raw_chapter}-{canonical_section}-*/research.md")
if tier3 not empty:
return { path: parent(tier3[0]), existing: true, tier: 3 }
# Tier 4: Flexible pattern with first keyword
keyword = canonical_slug.split('-')[0]
tier4 = Glob(".research/sections/*-{canonical_section}-*{keyword}*/research.md")
if tier4 not empty:
return { path: parent(tier4[0]), existing: true, tier: 4 }
# No match - use canonical for new directory
return { path: canonical_path, existing: false, tier: "new" }
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.
- 4d ago First seen · 308 lines · 34 tokens per session scan A f26a21e45ccd
continue is a command published in the GitHub repository BitYoungjae/marketplace (6 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 2,448 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.
Other commands, from other repositories
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
no-vibe
Enter no-vibe mode in OpenCode (tutor mode, no direct project file writes).
learn
LEARN MODE - Explains concepts with a gentle, Socratic, and human-like coaching persona.
OPSX: Onboard
Guided onboarding - walk through a complete OpenSpec workflow cycle with narration.
debrief
Post-engagement lessons learned analysis and debrief report.