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/JotJunior/cstkWrote 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/jotjunior/cstk/agente-00c-resume)<a href="https://agentmods.dev/commands/jotjunior/cstk/agente-00c-resume"><img src="https://agentmods.dev/badge/commands/jotjunior/cstk/agente-00c-resume/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/jotjunior/cstk/agente-00c-resume"><img src="https://agentmods.dev/badge/commands/jotjunior/cstk/agente-00c-resume.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.00051 | $0.07168 |
| Opus 5 | $0.00026 | $0.03584 |
| Sonnet 5 | $0.00010 | $0.01434 |
| Haiku 4.5 | $0.00005 | $0.00717 |
Grade A, and why
agente-00c-resume 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 8d 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 — 572 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/agente-00c-resume
Retomada de execucao 00C conforme contrato em
docs/specs/_archived/agente-00c/contracts/cli-invocation.md.
Argumentos recebidos
$ARGUMENTS
Comportamento esperado
Execute estes passos em ordem. Use os scripts em
~/.claude/skills/agente-00c-runtime/scripts/ para todas as operacoes
de estado — nao manipule state.json diretamente com jq.
1. Parse de argumentos
Extrair:
--projeto-alvo-path(default =cwd)--resposta-bloqueioopcional, formato<block-id>:<resposta>--init-aspectosopcional, JSON array de 3..7 strings — usado para re-inicializarinitial_key_aspectsem execucoes legadas (criadas antes da FASE 3 da evolucao, com aspectos=null). Forca overwrite viadrift.sh init --force.--init-aspectos-tecnicosopcional, JSON array 0..7 strings--init-aspectos-operacionaisopcional, JSON array 0..7 strings--allow-target-outside-sessionopcional; capturar em_scope_allow(--allow-outsidequando presente). Bypass explicito e auditado da validacao abaixo (issues #189/#190/#191).
Defina <SD> = <PAP>/.claude/agente-00c-state para os comandos abaixo.
Antes do lock, valide que <PAP> e a RAIZ DESTA SESSAO (mesma guarda da
secao 2 do /agente-00c: hooks de guarda e servidor MCP so operam sob a
raiz da sessao; retomar de outra raiz roda a onda SEM guarda enforced e
com toda tool MCP em SESSION_MISMATCH):
session-scope.sh check --projeto-alvo-path <PAP> $_scope_allow || exit 3
2. Adquirir lock
Fronteira command↔orquestrador: o lock e deste command PAI (acquire aqui, release SEMPRE no passo 7). O orquestrador NAO adquire/libera lock — ver "Fronteira command↔orquestrador" em
agente-00c-orchestrator.md.
state-lock.sh acquire --state-dir <SD>
Exit 3 = outra execucao em andamento neste projeto. Aborte com mensagem
clara apontando para /agente-00c-abort ou aguardar conclusao.
3. Validar estado
state-validate.sh --state-dir <SD>
state-rw.sh sha256-verify --state-dir <SD>
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.
- 8d ago Changed · +20 lines f766598b0ae4
- 12d ago First seen · 552 lines · 51 tokens per session scan A 23e46b605298
agente-00c-resume is a command published in the GitHub repository JotJunior/cstk (23 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 7,168 once invoked, about $0.0003 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-30.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.