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 skills add JotJunior/cstk --skill agente-00c-abortgit 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/skills/jotjunior/cstk/agente-00c-abort)<a href="https://agentmods.dev/skills/jotjunior/cstk/agente-00c-abort"><img src="https://agentmods.dev/badge/skills/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/skills/jotjunior/cstk/agente-00c-abort"><img src="https://agentmods.dev/badge/skills/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.00038 | $0.00288 |
| Opus 5.5 | $0.00015 | $0.00115 |
| Sonnet 5.5 | $0.00008 | $0.00058 |
| Haiku 4.5 | $0.00004 | $0.00029 |
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.
What it actually says
Abortar projeto no Codex
Leia ../feature-00c/references/lifecycle.md, seção Aborto. Use kind=project e execution.canonical_project do estado existente como short_name. Se a conexão MCP possuir a onda autorizada, aborte diretamente com cstk_abort. Caso contrário selecione o projeto absoluto da sessão, confira cstk_status e execute cstk_abort com o motivo recebido.
purge_backups somente quando explicitamente solicitado. Confira status, relatório .claude/agente-00c-report.md e commit_status. Preserve documentos, código, histórico e commits existentes. Respeite o lock de outro dono vivo e a proveniência da execução. Aborto não representa conclusão da pipeline.
Gotchas
- Use a identidade e o kind do estado existente; não faça bootstrap para abortar.
- Dono vivo ou desconhecido nunca é roubado; recuperação exige PID registrado comprovadamente morto.
- Origem Claude/desconhecida exige handoff autorizado com proveniência preservada.
- Purge de backups requer pedido explícito; artefatos e histórico são preservados.
- Aborto não significa conclusão; execução concluída não é reclassificada.
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 · 26 lines · 38 tokens per session scan A 03e7c574cdbb
agente-00c-abort is a skill published in the GitHub repository JotJunior/cstk (24 stars, last pushed 6d ago), licensed MIT. It adds 38 tokens to every session and 288 once invoked, about $0.0002 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-10-06.
Other skills, from other repositories
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
paperclip-board
Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.
paperclip-distill
Use when an operation issue is a Paperclip cursor-window, distill, or backfill. Turn source-bundled Paperclip activity into wiki-insightful project standups, durable project pages, decisions, and history without asset dereferencing.
summarize-status
Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.
paperclip-task-bridge
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.