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-featuresnpx skills add JotJunior/cstk --skill review-featuresgit 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-features)<a href="https://agentmods.dev/skills/jotjunior/cstk/review-features"><img src="https://agentmods.dev/badge/skills/jotjunior/cstk/review-features.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.1 | $0.00056 | $0.04598 |
| Opus 5 | $0.00028 | $0.02299 |
| Sonnet 5 | $0.00011 | $0.00920 |
| Haiku 4.5 | $0.00006 | $0.00460 |
Grade A, and why
review-features 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 6d 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 — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Revisar Portfolio de Features
Gere um relatorio comparativo de TODAS as features do projeto, com tabela agregada de progresso, criticidade pendente e sugestao de acao (arquivar, abandonar, priorizar ou continuar).
Pre-requisitos
Obrigatorio: pelo menos um diretorio agregador de features. Procurar nesta ordem:
docs/specs/*/— padrao SDD (cada feature em sua pasta comspec.md+tasks.md)docs/features/*/- Diretorio passado explicitamente pelo usuario
Cada subdiretorio deve conter pelo menos um tasks.md para entrar no
relatorio. spec.md e opcional (usado para extrair descricao).
Diferenca para review-task
| Aspecto | review-task | review-features |
|---|---|---|
| Escopo | UMA feature ou projeto | TODAS as features (cross-feature) |
| Saida | Status detalhado + top-3 tasks | Tabela comparativa + sugestao por feature |
| Atualiza arquivos? | Sim (marca tasks [x] baseado em evidencia) |
Nao (read-only) |
| Pergunta tipica | "qual a proxima task?" | "qual feature priorizar?" |
Se o usuario pediu progresso de UMA feature, use review-task. Se pediu
visao global ou comparacao entre features, use esta.
Proximos passos sugeridos
/review-taskem features marcadas comoPRIORIZARpara detalhar tasks/execute-taskna proxima task critica- Antes de mover uma feature
ARQUIVARparadocs/specs/_archived/<YYYY-MM-DD>-<feature>/, rodar o gate deterministicoscripts/delta-gate.sh docs/specs/<feature>/spec.md --corpus-dir docs/specs/current:- Exit != 0 (bloqueado): NAO mover a feature. Reportar ao operador os
FINDING|error|<code>|<mensagem>literais emitidos pelo gate e pedir que a secao## Delta Requirementsseja preenchida na spec, ou que um skip explicito seja registrado (vercontracts/delta-section-format.md). - Exit 0 (liberado): rodar
scripts/delta-merge.sh docs/specs/<feature>/spec.md --feature <feature>ANTES domvpara_archived/. Se o merge tambem bloquear (exit 1 — o corpus mudou entre o gate e o merge), omvfica igualmente suspenso (defesa em profundidade — o gate por si so nunca garante que o merge vai passar). - So apos o merge ter sucesso (exit 0) o
mvacontece — o fluxo de mover para_archived/permanece EXATAMENTE como hoje (acao manual, pedir confirmacao ao usuario antes de mover;<YYYY-MM-DD>e a data em que a acao de arquivamento de fato ocorre, nao a data de criacao da feature — permite ordenacao cronologica do diretorio sem abrir cada subpasta). Diretorios ja existentes sobdocs/specs/_archived/sem esse prefixo de data (arquivados antes desta convencao) permanecem inalterados — NAO renomear nem mover conteudo ja arquivado. O corpus canonico (docs/specs/current/) e ADICIONAL ao archive existente, nunca uma substituicao (FR-006).
- Exit != 0 (bloqueado): NAO mover a feature. Reportar ao operador os
What ships with it
7 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.
- 6d ago First seen · 390 lines · 56 tokens per session scan A 27f1eb4f1f17
review-features is a skill published in the GitHub repository JotJunior/cstk (23 stars, last pushed 3d ago), licensed MIT. It adds 56 tokens to every session and 4,598 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.