feature-00c-clarify-asker

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

A helper agent for the clarify stage of a specification process, where a team resolves open questions before building one feature. It produces one to five structured questions and does not make decisions or edit project files.

In plain words
What is it for?
Use it to find unanswered questions about a feature’s specification, existing project briefing, rules, and earlier decisions.
Why use it?
It separates question-asking from decision-making, helping the main coordinator identify missing requirements without changing the project.

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 to find unanswered questions about a feature’s specification, existing project briefing, rules, and earlier decisions.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/jotjunior/cstk/feature-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 feature-00c-clarify-asker

README.md
[![agentmods](https://agentmods.dev/badge/agents/jotjunior/cstk/feature-00c-clarify-asker.svg)](https://agentmods.dev/agents/jotjunior/cstk/feature-00c-clarify-asker)
Your own site
<a href="https://agentmods.dev/agents/jotjunior/cstk/feature-00c-clarify-asker"><img src="https://agentmods.dev/badge/agents/jotjunior/cstk/feature-00c-clarify-asker.svg" alt="Measured on agentmods" height="20"></a>
Per session 67 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,209 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.00067 $0.01209
Opus 5 $0.00034 $0.00605
Sonnet 5 $0.00013 $0.00242
Haiku 4.5 $0.00007 $0.00121

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

Security

Grade A, and why

feature-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 8d 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/feature-00c-clarify-asker.md · 112 lines

How it starts

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

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

Diferenca face ao agente-00c-clarify-asker: voce opera no escopo de UMA feature dentro de projeto que JA tem briefing + constitution ratificados. Nao ha suggested_stack como input (a stack ja foi decidida no projeto). Spec corrente substitui stack como terceira fonte de contexto.

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 do projeto
constitution_path string Caminho absoluto de docs/constitution.md do projeto
current_stage string Tipicamente clarify
decisoes_anteriores array Decisoes ja tomadas em ondas anteriores (evita 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: gerado pela skill specify (ou edit anterior).
    • briefing.md: contexto fundacional do projeto-alvo.
    • constitution.md: principios do projeto.
  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>" }
      ]
    }
  ]
}

Read the full file on GitHub · 112 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. 8d ago First seen · 112 lines · 67 tokens per session scan A 3b35b3a9d947

Subscribe to this mod's changes

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