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 voro6yov/spec-driven-development --skill update-reportsgit clone --depth 1 https://github.com/voro6yov/spec-driven-developmentWrote 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/voro6yov/spec-driven-development/update-reports)<a href="https://agentmods.dev/skills/voro6yov/spec-driven-development/update-reports"><img src="https://agentmods.dev/badge/skills/voro6yov/spec-driven-development/update-reports/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/voro6yov/spec-driven-development/update-reports"><img src="https://agentmods.dev/badge/skills/voro6yov/spec-driven-development/update-reports.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.00061 | $0.00540 |
| Opus 5.5 | $0.00024 | $0.00216 |
| Sonnet 5.5 | $0.00012 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
update-reports 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.
What it actually says
Update Reports (spec-core)
The spec-update detector reports are the data contracts of the cross-layer update cascade that spec-core:update-specs orchestrates. Each layer's detector produces one; downstream layers parse them by these schemas. They are homed here in spec-core — next to the orchestrator — because they are consumed across plugin boundaries (a domain-diagram diff drives persistence, application, REST API, and messaging; the application-service and ops diffs drive REST API and messaging).
Each schema is a supporting file in a sibling folder; Read it by path. Only this index is auto-loaded by frontmatter — the per-layer docs are not.
| Schema | Path | Produced by | Describes |
|---|---|---|---|
| domain | domain/index.md | domain-spec:updates-detector |
<stem>.domain/updates.md — the class-grouped domain-diagram diff + stereotype→category footer |
| application-axis | application/index.md | application-spec:{commands,queries}-updates-detector |
<stem>.application/{commands,queries}-updates.md — the application-service diagram diff |
| ops | ops/index.md | application-spec:ops-updates-detector |
<stem>.application/ops-updates.md — the per-<op-name> ops-service diagram diff |
Resolution. A consumer that auto-loads spec-core:update-reports via frontmatter resolves <update_reports_dir> as the directory containing this SKILL.md (its loaded context reveals its location), then Reads <update_reports_dir>/<layer>/index.md. Hard-fail on a missing path; never skip silently.
Not homed here. Each layer's own code-update report (<stem>.persistence/updates.md, <stem>.application/updates.md, <stem>.rest-api/updates.md, <stem>.messaging/updates.md) — the ## Affected Artifacts dispatch schema each plugin's update-code flow consumes — remains a plugin-private supporting file under that plugin's own patterns umbrella. Only the cross-consumed detector schemas live here.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 22 lines · 61 tokens per session scan A f11fc222f40b
update-reports is a skill published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 13d ago), licensed Apache-2.0. It adds 61 tokens to every session and 540 once invoked, about $0.0002 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-04.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…