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-abort)<a href="https://agentmods.dev/commands/jotjunior/cstk/agente-00c-abort"><img src="https://agentmods.dev/badge/commands/jotjunior/cstk/agente-00c-abort/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-abort"><img src="https://agentmods.dev/badge/commands/jotjunior/cstk/agente-00c-abort.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.01630 |
| Opus 5 | $0.00018 | $0.00815 |
| Sonnet 5 | $0.00007 | $0.00326 |
| Haiku 4.5 | $0.00004 | $0.00163 |
Grade A, and why
agente-00c-abort 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 10d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/agente-00c-abort
Aborto manual de execucao 00C conforme contrato em
docs/specs/_archived/agente-00c/contracts/cli-invocation.md.
Argumentos recebidos
$ARGUMENTS
Comportamento esperado
Use os scripts em ~/.claude/skills/agente-00c-runtime/scripts/. Aborto
e operacao terminal — depois dela a execucao nao pode mais ser retomada
(/agente-00c-resume em estado abortado retorna mensagem informativa).
1. Parse de argumentos
Extrair --projeto-alvo-path (default = cwd). Defina:
<PAP>= projeto-alvo-path<SD>=<PAP>/.claude/agente-00c-state
2. Validar pre-condicoes
2.a. Estado existe?
# Backend-agnostico (state-db-runtime-parity, v6.3): sob backend SQLite o
# estado e state.db, nao state.json. Checar so state.json tornaria
# impossivel abortar execucao iniciada apos `cstk state enable-sqlite`.
[ -f <SD>/state.json ] || [ -f <SD>/state.db ] \
|| die "Nao ha execucao 00C em <PAP>."
Se nao existe, retorne mensagem clara e termine (exit 0 — operador pode ter chamado abort em projeto errado, nao e erro tecnico).
2.b. Adquirir lock
state-lock.sh acquire --state-dir <SD>
Exit 3 = outra execucao em andamento. Aborte com mensagem orientando aguardar conclusao da onda em andamento OU usar /agente-00c-abort apos a onda corrente fechar.
2.c. Validar schema
state-validate.sh --state-dir <SD>
Schema invalido = aviso especial (NAO bloqueia o abort — operador pode querer abortar exatamente porque o estado esta corrompido). Continue mesmo com warning, mas registre em stderr:
AVISO: schema do state.json invalido. Aborto procedera mesmo assim.
Operador deve inspecionar manualmente <SD>/state.json apos abort.
3. Verificar idempotencia
status=$(state-rw.sh get --state-dir <SD> --field '.execution.status')
Se status ja e terminal (abortada ou concluida):
Execucao em status <status>. Nada a abortar.
Relatorio final: <PAP>/.claude/agente-00c-report.md (se existir)
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.
- 10d ago First seen · 192 lines · 36 tokens per session scan A 0fdda99be4c1
agente-00c-abort is a command published in the GitHub repository JotJunior/cstk (23 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,630 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-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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.