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-proposegit 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-propose)<a href="https://agentmods.dev/skills/jnerytech/specd/specd-propose"><img src="https://agentmods.dev/badge/skills/jnerytech/specd/specd-propose/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-propose"><img src="https://agentmods.dev/badge/skills/jnerytech/specd/specd-propose.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.00087 | $0.02052 |
| Opus 5.5 | $0.00035 | $0.00821 |
| Sonnet 5.5 | $0.00017 | $0.00410 |
| Haiku 4.5 | $0.00009 | $0.00205 |
Grade A, and why
specd-propose 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specd-propose
Segundo passo do ciclo. Transforma explore/notes.md em delta.md. Não toca
no código e não escreve em .specd/specs/.
Antes de qualquer coisa
specd --version
Menor que requires_specd → pare, nomeando a instalada e a exigida.
1. Ler a exploração
explore/notes.md da change. Se o código mudou desde que ele foi escrito, o
explore está vencido: volte para specd-explore antes de propor. Explore
vencido é a forma mais barata de produzir proposta ancorada em símbolo que já
não existe.
2. Ler a spec efetiva
specd spec --json
É daqui que sai o que já existe. Nunca reconstrua o overlay lendo
.specd/specs/ e os deltas soltos.
Todo REQ-ID citado é conferido nesta saída antes de entrar em qualquer texto.
3. Escrever o delta
.specd/changes/<nome>/delta.md:
---
change: 2026-08-01-escopo
target: [capability-a, capability-b]
---
## ADDED
### REQ-XXX-001 — Título curto
**Capability.** capability-a
**Statement.** The specd <sujeito> SHALL <comportamento>.
**Acceptance.**
- critério verificável
- outro critério verificável
Prosa explicando por que, e o que foi medido. Não é decoração: é o que impede
a próxima pessoa de desfazer a decisão sem saber que existiu.
```yaml anchors
- file: src/modulo/arquivo.ts
symbol: "export function nome"
```
Regras que o gate cobra:
- Um
SHALLpor statement. Dois comportamentos são dois requisitos. - EARS: ubiquitous, event-driven (
WHEN), state-driven (WHILE), unwanted-behaviour (IF … THEN), optional-feature (WHERE). ADDEDdeclara**Capability.**;MODIFIEDpode omitir — o destino é a capability que já contém o ID.MODIFIEDcarrega o texto completo, não um patch.REMOVEDaceita só a lista de identificadores.- Identificador aposentado nunca é reusado.
- A âncora é
fileobrigatório esymbolopcional, e o símbolo é procurado literalmente:export async function feexport function fsão strings diferentes.
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 · 215 lines · 87 tokens per session scan A d039666a8952
specd-propose is a skill published in the GitHub repository jnerytech/specd (0 stars, last pushed 2mo ago), licensed MIT. It adds 87 tokens to every session and 2,052 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
ospec-goal
Create or advance a full OSpec goal using the current document, task graph, worker, review, and evidence workflow.
ospec
Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
ospec-change
Create or advance a lightweight OSpec change using the classic fast workflow.
spec-generator
Usa esta skill cuando el usuario pida crear, redactar o revisar una especificación (spec) de una funcionalidad. Guía una entrevista de requisitos y produce un spec.md siguiendo la plantilla del equipo.
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…