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 commands/jotjunior/cstk/feature-00cgit 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/feature-00c)<a href="https://agentmods.dev/commands/jotjunior/cstk/feature-00c"><img src="https://agentmods.dev/badge/commands/jotjunior/cstk/feature-00c.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.00080 | $0.19169 |
| Opus 5 | $0.00040 | $0.09584 |
| Sonnet 5 | $0.00016 | $0.03834 |
| Haiku 4.5 | $0.00008 | $0.01917 |
Grade D, and why
feature-00c scanned grade D with 3 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 today.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
> no descritor (`chmod 600`) e no prompt do spawn (SEC-H3: roteamento por Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
<projeto-alvo>/.claude/settings.json, que pode estar versionado Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
if [ -f "$_proj/.mcp.json" ] && grep -q '"cstk-state"' "$_proj/.mcp.json" 2>/dev/null; then How it starts
The opening of the file, as written. The whole thing — 1,324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/feature-00c
Voce vai iniciar uma execucao do orquestrador autonomo feature-00c
conforme contrato em docs/specs/_archived/feature-00c/contracts/cli-invocation.md.
Fronteira command↔orquestrador (lock + init): este command PAI detem o lock (acquire no passo 7, release SEMPRE no Cleanup) e inicializa o
state.json(passo 3). O orquestrador NAO adquire lock nem re-inicializa estado — contrato canonico em "Fronteira command↔orquestrador" deagente-00c-feature-orchestrator.md. Identico no resume (/feature-00c-resume).
Argumentos recebidos
$ARGUMENTS
Comportamento esperado
0. Warm-up de permissoes (CRITICO — antes de qualquer outra coisa)
A pipeline feature-00c invoca varias skills/tools ao longo de ondas. Permissoes pedidas "lazy" quebram a autonomia se o operador nao estiver presente. Solucao: invocar TODAS as skills/tools em batch ANTES de qualquer logica.
Apresente ao operador:
Feature-00C — Warm-up de permissoes
Vou agora invocar cada skill/tool que sera usada na pipeline para
disparar TODOS os prompts de permissao em batch. Voce sera questionado
sobre cada uma; aprove para autorizar a execucao autonoma posterior.
Continuar? [s/N]
Se confirmado, execute em sequencia (cada item dispara o prompt nativo):
| # | Tool/Skill | Modo de warm-up |
|---|---|---|
| 1 | tool Skill — specify |
invocar com prompt minimo "responda OK" |
| 2 | tool Skill — clarify |
idem |
| 3 | tool Skill — plan |
idem |
| 4 | tool Skill — checklist |
idem |
| 5 | tool Skill — create-tasks |
idem |
| 6 | tool Skill — execute-task |
idem |
| 7 | tool Skill — review-task |
idem |
| 8 | tool Skill — validate-documentation (Quality Gate) |
invocar com --help ou prompt minimo "responda OK" |
| 9 | tool Skill — validate-docs-rendered (Quality Gate) |
idem |
| 10 | tool Skill — owasp-security (Quality Gate) |
idem |
| 11 | tool Agent — agente-00c-feature-orchestrator |
spawn com prompt "warm-up: responda READY" |
| 12 | tool Agent — feature-00c-clarify-asker |
idem |
| 13 | tool Agent — feature-00c-clarify-answerer |
idem |
| 14 | tool ScheduleWakeup | delaySeconds: 60 + prompt: "warm-up no-op" |
| 15 | tool Bash — state-rw.sh --help |
dispara permissao Bash |
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.
- today Changed · +91 lines 814c29752ee0
- 4d ago First seen · 1,233 lines · 80 tokens per session scan D 8d1742d7b58d
feature-00c is a command published in the GitHub repository JotJunior/cstk (23 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 19,169 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, reads agent configuration directories, reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.