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-new-spec/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-new-spec)<a href="https://agentmods.dev/skills/jentic/jentic-api-scorecard/sdd-new-spec"><img src="https://agentmods.dev/badge/skills/jentic/jentic-api-scorecard/sdd-new-spec/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-new-spec"><img src="https://agentmods.dev/badge/skills/jentic/jentic-api-scorecard/sdd-new-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 191 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
- low Tool Misuse · line 191 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00141 | $0.04746 |
| Opus 5 | $0.00071 | $0.02373 |
| Sonnet 5 | $0.00028 | $0.00949 |
| Haiku 4.5 | $0.00014 | $0.00475 |
Grade A, and why
sdd-new-spec 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdd-new-spec — scaffold a feature spec for a roadmap phase
You are operating within a Spec-Driven Development (SDD) workflow. See .claude/rules/sdd-constitution.md.
The constitution (mission / tech-stack / roadmap) already exists in specs/. This skill takes one phase from specs/roadmap.md and turns it into a workable feature spec — a dated directory under specs/ with three files: requirements (what + why), plan (how), validation (done).
Inputs
Argument in $ARGUMENTS (optional):
- empty → list candidate phases and ask the user to pick
- integer (
1,7) → use that phase number directly - title fragment (
"local service routing") → case-insensitive match against phase titles; if ambiguous, list matches and ask
Hard constraints
- Spec-only — zero code changes. This skill never modifies any code tree,
docs/,CLAUDE.md, or any implementation/doc file outsidespecs/<date>-<slug>/. It does not run test suites or linters against code. The only files it touches are the three it scaffolds. The PR it opens is for review of the spec itself; the implementation that the spec describes happens in a follow-up PR. - Do not write to disk before the Phase 4 AskUserQuestion step completes. The grouped questions exist to lock in decisions that shape the files; writing early wastes the call.
- AskUserQuestion groups exactly three questions, one per output file (requirements, plan, validation). Issue them in a single call.
- Do not create a new roadmap phase. If the user wants one, tell them edits to
specs/roadmap.mdare a separate explicit action — this skill only materializes existing phases. - Ground every requirement and constraint in
specs/mission.md,specs/tech-stack.md, or the roadmap phase itself. Do not invent scope the sources do not support. - PR contains the spec, nothing else. Staged set must be exactly the three files under
specs/<date>-<slug>/before committing. If anything else appears, stop and surface it.
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 · 263 lines · 141 tokens per session scan A 2131cc82c9b9
sdd-new-spec is a skill published in the GitHub repository jentic/jentic-api-scorecard (21 stars, last pushed today), licensed Apache-2.0. It adds 141 tokens to every session and 4,746 once invoked, about $0.0007 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…