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 skills add jnerytech/specd --skill specd-exploregit clone --depth 1 https://github.com/jnerytech/specdWrote 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/jnerytech/specd/specd-explore)<a href="https://agentmods.dev/skills/jnerytech/specd/specd-explore"><img src="https://agentmods.dev/badge/skills/jnerytech/specd/specd-explore/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.
<a href="https://agentmods.dev/skills/jnerytech/specd/specd-explore"><img src="https://agentmods.dev/badge/skills/jnerytech/specd/specd-explore.svg" alt="Reviewed on agentmods" width="80" 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.00088 | $0.01473 |
| Opus 5.5 | $0.00035 | $0.00589 |
| Sonnet 5.5 | $0.00018 | $0.00295 |
| Haiku 4.5 | $0.00009 | $0.00147 |
Grade A, and why
specd-explore 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 12d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specd-explore
Primeiro passo do ciclo explore → propose → apply → archive. Abre a change e
produz o registro da exploração. Não escreve delta, não altera código, não
transiciona nada no board.
Antes de qualquer coisa
specd --version
Se a versão for menor que a declarada em requires_specd, pare e diga qual
está instalada e qual é necessária. Uma skill que segue contra uma CLI velha
acaba reconstruindo à mão o que o comando ausente decidiria — que é exatamente o
erro que ela existe para evitar.
1. Ler o modo do repositório
specd status --json
O modo vem da configuração, nunca da aparência do repositório:
[board] providerdefinido → modo com board- ausente → modo sem board
[board] card diz se toda change precisa declarar o card de onde nasceu:
required (padrão onde há board) ou optional.
Nunca conclua "parece que aqui tem board". Isso é decidir o ciclo por
semelhança, e o princípio no-guessing-on-conflict proíbe.
2. Estabelecer o escopo
Com board. Resolver a tarefa é obrigatório quando card = "required". Sem
card resolvido não há change. Se a busca devolver mais de um candidato plausível
ou nenhum, pare e pergunte pela ferramenta de pergunta do host, com os
candidatos como opções — não escolha "o mais parecido" nem siga sem card.
Sem board. O escopo vem da descrição de quem roda a skill, e é registrado em
explore/notes.md com a mesma cerimônia que uma issue teria. Escopo dito de
boca e não escrito não sobrevive à próxima sessão (memory-is-ephemeral).
3. Abrir a change
O nome é kebab-case com prefixo de data: AAAA-MM-DD-escopo. Crie
.specd/changes/<nome>/proposal.md com a frontmatter:
---
change: 2026-08-01-escopo
status: active
card:
ref: "4821"
url: "https://board.example/issues/4821"
---
card só entra quando existe card. Onde [board] card = "required", a camada
schema do gate reprova a change sem ele.
4. Ler a spec efetiva
specd spec --json
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.
- 12d ago First seen · 151 lines · 88 tokens per session scan A 08459a7aa88a
specd-explore is a skill published in the GitHub repository jnerytech/specd (0 stars, last pushed 2mo ago), licensed MIT. It adds 88 tokens to every session and 1,473 once invoked, about $0.0004 per session on Opus 5.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-10-02.
Other skills, from other repositories
openspec-schema-authoring
Create or customize OpenSpec workflow schemas in this repository using openspec schema init and openspec schema fork. Use when the user wants to add, fork, or validate a schema under openspec/schemas/.
openspec-linearized
Use whenever Codex operates on an OpenSpec change lifecycle or artifact, including propose/new change, apply/implement tasks, archive/finalize, sync specs, continue/update artifacts, validate/status checks, or work under openspec/changes/. This is the Linear lifecycle overlay for OpenSpec work: bind Linear issues…
openspec-bulk-apply-change
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
spec-manager
Spec-driven project iteration workflow: L1 PRD -> L2 Design -> L3 Impl -> Agent Task, with human review gates at each layer.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.