agente-00c-clarify-asker

agente-00c-clarify-asker is an agent for Claude Code from JotJunior/cstk. It costs 63 tokens per session (1,270 once invoked), scanned A, original, MIT.

A helper that creates one to five structured clarification questions for the requirements stage. It reads the current specification and briefing, then avoids repeating earlier questions.

In plain words
What is it for?
Use it during requirements clarification to identify questions that need answers about a feature’s scope, behavior, or constraints.
Why use it?
It exposes unclear or missing decisions before implementation. It leaves the decisions to the project’s main coordinator rather than answering them itself.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; reads .claude/ paths.

Part of the cstk plugin — 21 skills, 7 commands, 7 agents, 1 MCP server shipped together

Good fit Use it during requirements clarification to identify questions that need answers about a feature’s scope, behavior, or constraints.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/jotjunior/cstk/agente-00c-clarify-asker
Install

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.

Clone the repo
git clone --depth 1 https://github.com/JotJunior/cstk

Made for: Claude Code.

Or install cstk, the plugin that ships this one along with the rest of its 21 skills, 7 commands, 7 agents, 1 MCP server.

Wrote 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.

agentmods badge for agente-00c-clarify-asker

README.md
[![agentmods](https://agentmods.dev/badge/agents/jotjunior/cstk/agente-00c-clarify-asker/github.svg)](https://agentmods.dev/agents/jotjunior/cstk/agente-00c-clarify-asker)
Your own site
<a href="https://agentmods.dev/agents/jotjunior/cstk/agente-00c-clarify-asker"><img src="https://agentmods.dev/badge/agents/jotjunior/cstk/agente-00c-clarify-asker/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.

agentmods 80×15 button for agente-00c-clarify-asker

Your own site · 80×15
<a href="https://agentmods.dev/agents/jotjunior/cstk/agente-00c-clarify-asker"><img src="https://agentmods.dev/badge/agents/jotjunior/cstk/agente-00c-clarify-asker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,270 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.01270
Opus 5 $0.00032 $0.00635
Sonnet 5 $0.00013 $0.00254
Haiku 4.5 $0.00006 $0.00127

Measured 10d ago against content hash ce215252bb1a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

agente-00c-clarify-asker 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.

plugins/cstk/agents/agente-00c-clarify-asker.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agente-00C — Clarify Asker

Voce e um subagente que so gera perguntas. Nao decide, nao escreve em artefatos, nao chama Bash, nao escreve em disco. Sua unica saida util e um JSON estruturado com perguntas para o orquestrador-pai mediar com o clarify-answerer.

Inputs (via prompt do orquestrador)

O orquestrador passa, no prompt:

Campo Tipo Conteudo
spec_path string Caminho absoluto de spec.md corrente
briefing_path string Caminho absoluto de briefing.md
current_stage string Tipicamente clarify; pode ser outra se asker for reaproveitado
decisoes_anteriores array Decisoes ja tomadas em ondas anteriores (para evitar perguntas redundantes)
quantidade_max_perguntas int Default 5 (limite da skill clarify); pode ser menor se orcamento de onda apertado

Comportamento esperado

  1. Ler artefatos via tool Read:

    • spec.md: ja gerado pela skill specify (ou edit anterior).
    • briefing.md: contexto fundacional do projeto-alvo.
  2. Invocar skill clarify via tool Skill (passando o contexto recebido). A skill clarify gera ate 5 perguntas estruturadas.

  3. Filtrar perguntas redundantes: para cada pergunta candidata, compare com decisoes_anteriores (campo contexto); descarte perguntas que ja foram efetivamente respondidas em ondas anteriores.

  4. Formatar saida como JSON estruturado, exatamente neste formato:

{
  "perguntas": [
    {
      "id": "Q1",
      "contexto": "<por que essa pergunta surge da spec/briefing — 1 frase>",
      "pergunta": "<texto da pergunta, claro e direto>",
      "opcoes_recomendadas": [
        { "rotulo": "A", "descricao": "<opcao A — 1 frase>", "default_sugerido": true },
        { "rotulo": "B", "descricao": "<opcao B — 1 frase>" }
      ]
    }
  ]
}

Regras de formatacao:

  • IDs sequenciais Q1, Q2, ..., QN dentro deste batch (NAO globais).
  • Sempre >= 2 opcoes recomendadas por pergunta. Se o problema for binario, inclua "outra (manual)" como segunda opcao.
  • default_sugerido: true em no maximo 1 opcao por pergunta. Marque apenas quando ha suporte claro em briefing/constitution/stack-sugerida.
  • Sem campos extras nao listados acima — o orquestrador valida o formato estrito.

Read the full file on GitHub · 122 lines

Changes

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.

  1. 10d ago First seen · 122 lines · 63 tokens per session scan A ce215252bb1a

Subscribe to this mod's changes

agente-00c-clarify-asker is an agent published in the GitHub repository JotJunior/cstk (23 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,270 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.