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-archive-changegit 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-archive-change)<a href="https://agentmods.dev/skills/jnerytech/specd/specd-archive-change"><img src="https://agentmods.dev/badge/skills/jnerytech/specd/specd-archive-change/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-archive-change"><img src="https://agentmods.dev/badge/skills/jnerytech/specd/specd-archive-change.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.00076 | $0.01461 |
| Opus 5.5 | $0.00030 | $0.00584 |
| Sonnet 5.5 | $0.00015 | $0.00292 |
| Haiku 4.5 | $0.00008 | $0.00146 |
Grade A, and why
specd-archive-change 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specd-archive-change
Último passo do ciclo. Aplica o delta na verdade realizada e move a change. Não implementa e não conserta gate vermelho.
Antes de qualquer coisa
specd --version
Menor que requires_specd → pare.
O que este passo significa
Arquivar promove os requisitos do delta de origin: delta para
origin: specs. A partir daí, âncora quebrada neles é erro, não warning.
É uma promoção de rigor: arquivar é assumir dívida de manutenção sobre cada âncora promovida. É o momento mais caro do ciclo, e o que mais merece cerimônia.
1. Pré-condições duras
specd verify
Verde, sem exceção. Gate vermelho volta para specd-apply-change — esta skill
não conserta nada.
Toda task da change precisa estar done com SHA em evidence.commits. É
pré-condição dura, não pergunta: task aberta significa trabalho que a change
declarou e não entregou, e arquivar promove o requisito dela a verdade
realizada mesmo assim.
O CLI não impõe isso — archive não olha o status das tasks. A regra vive aqui,
o que quer dizer que ela pode ser esquecida; enquanto for assim, esta skill é o
único lugar que a cobra.
Não existe arquivamento provisório, nem arquivamento que deixa o board para depois.
Rever o que mudou desde o propose
Uma pergunta só, e sobre um recorte estreito: a âncora realiza o que o statement afirma?
O recorte é lido, não deduzido. A fonte é o propose.json que a
specd-propose gravou na change; o estado de agora vem de specd spec --json e
do relatório do gate.
Entram na revisão:
- requisito cujo statement ou critérios diferem do registrado
- requisito ausente do registro — o passo 4 da
specd-apply-changemanda escrever no delta o que a execução descobriu, e esse requisito não passou pela revisão do propose; é o caminho mais provável de enunciado ruim, escrito sob pressão de implementação - âncora que o registro anotou pendurada e que hoje resolve — mesmo com a declaração inalterada, porque o que mudou foi o símbolo passar a existir
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 · 155 lines · 76 tokens per session scan A fe42ae371f6f
specd-archive-change is a skill published in the GitHub repository jnerytech/specd (0 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 1,461 once invoked, about $0.0003 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.