Borrowing it
Nothing to install: this file belongs to jentic/jentic-api-scorecard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jentic/jentic-api-scorecard/main/.claude/skills/sdd-distill-lessons/SKILL.mdgit clone --depth 1 https://github.com/jentic/jentic-api-scorecardWrote 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/jentic/jentic-api-scorecard/sdd-distill-lessons)<a href="https://agentmods.dev/skills/jentic/jentic-api-scorecard/sdd-distill-lessons"><img src="https://agentmods.dev/badge/skills/jentic/jentic-api-scorecard/sdd-distill-lessons/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/jentic/jentic-api-scorecard/sdd-distill-lessons"><img src="https://agentmods.dev/badge/skills/jentic/jentic-api-scorecard/sdd-distill-lessons.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.02120 |
| Opus 5 | $0.00038 | $0.01060 |
| Sonnet 5 | $0.00015 | $0.00424 |
| Haiku 4.5 | $0.00008 | $0.00212 |
Grade A, and why
sdd-distill-lessons 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 10d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdd-distill-lessons — distil retrospectives into specs/lessons.md
You are operating within a Spec-Driven Development (SDD) workflow. See .claude/rules/sdd-constitution.md.
This skill is the manual roll-up step of the SDD feedback loop. Per-spec specs/<date>-<slug>/retrospective.md files capture what individual specs missed; this skill reads them, deduplicates lessons across retrospectives, and writes the durable additions into specs/lessons.md so /sdd-new-spec and /sdd-new-phase consume them on their next run. When a lesson recurs across multiple retrospectives and clearly names a load-bearing invariant, the skill flags it as a specs/tech-stack.md promotion candidate for the user to hand-promote.
Hard constraints
specs/lessons.mdonly — no other writes. This skill edits exactly one file.specs/tech-stack.mdpromotions are surfaced as user-actionable suggestions; the skill never editstech-stack.md. Retrospectives are read-only.- Do not write to disk before the AskUserQuestion confirmation completes. The grouped lesson candidates exist to lock in what gets captured; writing early wastes the call.
- No git actions. This skill writes files and stops. Branching, committing, and PR creation are user actions per
.claude/rules/git-workflow.md. - Ground every proposed lesson in at least one retrospective. Do not invent lessons; do not paraphrase a retrospective into a lesson it does not actually support.
- Dedupe before proposing. If two retrospectives surface the same lesson (semantically), group them into one candidate referencing both retrospectives — do not propose duplicate bullets.
- Do not re-propose already-captured lessons. Compare each candidate against the existing
specs/lessons.mdbody and skip anything substantively present.
Phase 0 — Load context
Load in parallel:
- @specs/mission.md
- @specs/tech-stack.md
- @specs/lessons.md
- @.claude/rules/sdd-constitution.md
Enumerate specs/*/retrospective.md files (every dated feature-spec directory may or may not have one — retrospectives are optional). Load each in parallel via Read.
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.
- 10d ago First seen · 122 lines · 76 tokens per session scan A 06eadf5d486d
sdd-distill-lessons is a skill published in the GitHub repository jentic/jentic-api-scorecard (21 stars, last pushed today), licensed Apache-2.0. It adds 76 tokens to every session and 2,120 once invoked, about $0.0004 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.
Other skills, from other repositories
scalar-design-system
Scalar's design system — design tokens, theming (@scalar/themes), CSS variables, and the @scalar/components library. Use when designing or implementing Scalar UI, especially with Paper (code-to-design / design-to-code), so output matches real Scalar tokens, colors, typography, spacing, and components instead of…
lap
LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…
lap
LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…
fastapi-expert
Expert-level FastAPI development for high-performance Python APIs with async support. Use when the user mentions Python, API, async, REST, OpenAPI, or Pydantic, or when the task involves FastAPI Features.
openapi-expert
Expert-level OpenAPI/Swagger specification for API design, documentation, and code generation. Use when the user mentions swagger, API specs, REST, API design, or documentation, or when the task involves OpenAPI Specification, Webhooks, or Polymorphism.
api-integrations
Expose external APIs to Falcon Foundry via OpenAPI specs. TRIGGER when user asks to "create an API integration", "adapt an OpenAPI spec for Foundry", "expose an API to workflows", "connect to a third-party API", or runs foundry api-integrations create. Also trigger when user has an OpenAPI/Swagger spec and wants it…