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 review-taskgit 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/review-task)<a href="https://agentmods.dev/skills/jotjunior/cstk/review-task"><img src="https://agentmods.dev/badge/skills/jotjunior/cstk/review-task/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/review-task"><img src="https://agentmods.dev/badge/skills/jotjunior/cstk/review-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 650 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00056 | $0.09950 |
| Opus 5.5 | $0.00022 | $0.03980 |
| Sonnet 5.5 | $0.00011 | $0.01990 |
| Haiku 4.5 | $0.00006 | $0.00995 |
Grade A, and why
review-task 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 24d 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 — 780 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Revisar Status das Tarefas
Analise o arquivo de tarefas do projeto e gere um relatorio de status.
Contrato de saida (invariante): esta skill e READ-ONLY de relatorio — emite o status na conversa (stdout) e nunca cria nem escreve arquivo de relatorio (
.md,report.*, etc.). So persista quando o usuario pedir explicitamente. Marcar tarefa como concluida (editartasks.md) e trabalho do/execute-task, nao do review-task.
Pre-requisitos
Obrigatorio: arquivo de tasks existente em alguma das localizacoes
suportadas (docs/specs/*/tasks.md, docs/tasks.md, docs/tasks-*.md,
tasks.md, TODO.md).
Proximos passos
/execute-task {id}— iniciar a proxima tarefa recomendada pelo relatorio- Resolver dependencias apontadas como "bloqueadoras"
/analyze— se o relatorio revelar muitas tarefas sem evidencia de conclusao
Instrucoes de Revisao
1. Deteccao de Contexto do Projeto
Identifique o tipo de projeto para contextualizar a analise:
| Tipo | Indicadores |
|---|---|
| Documentacao | docs/ com .md, ausencia de src/, casos de uso (UC-*) |
| Codigo | src/, app/, lib/, package.json, composer.json |
| Misto | Contem tanto docs/ quanto codigo-fonte |
2. Localizacao do Arquivo de Tarefas
Procure na seguinte ordem:
docs/tasks.mdtasks.mdTODO.mddocs/TODO.md.github/TODO.md- Issues do repositorio (se aplicavel)
3. Analise das Tarefas
Para cada tarefa identificada, verifique:
Status Possiveis
- Pendente: Nao iniciada (
[ ]) - Em Andamento: Parcialmente concluida (
[~]) - Concluida: Finalizada (
[x]) - Bloqueada: Aguardando dependencia (
[!])
Checklist de Analise
- Identificar todas as tarefas e subtarefas
- Verificar status marcado vs status real
- Detectar inconsistencias (feito mas nao marcado)
- Identificar dependencias entre tarefas
- Calcular progresso por categoria/prioridade
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 24d ago Changed · +1 lines c5bd36ccd15c
- 1mo ago First seen · 779 lines · 56 tokens per session scan A cdf58e8029f9
review-task is a skill published in the GitHub repository JotJunior/cstk (24 stars, last pushed 4d ago), licensed MIT. It adds 56 tokens to every session and 9,950 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-08-30.
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.