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 skills/jotjunior/cstk/review-tasknpx 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.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.00056 | $0.09927 |
| Opus 5 | $0.00028 | $0.04963 |
| Sonnet 5 | $0.00011 | $0.01985 |
| Haiku 4.5 | $0.00006 | $0.00993 |
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 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 — 779 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.
- 4d ago First seen · 779 lines · 56 tokens per session scan A cdf58e8029f9
review-task is a skill published in the GitHub repository JotJunior/cstk (23 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 9,927 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 skills, from other repositories
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
omd:issue
불만은 채팅에 남으면 사라진다. 이 스킬은 불만을 kwakseongjae/oh-my-design의 GitHub 이슈로 옮겨 처리 가능한 큐로 만들고, 그 큐를 비우는 배치 verb까지 제공한다.
implementation-readiness
Verify BRD-lite, PRD, SRS/FRS, UX, and test prerequisites before implementation starts.