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-phase/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-phase)<a href="https://agentmods.dev/skills/jentic/jentic-api-scorecard/sdd-new-phase"><img src="https://agentmods.dev/badge/skills/jentic/jentic-api-scorecard/sdd-new-phase/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-phase"><img src="https://agentmods.dev/badge/skills/jentic/jentic-api-scorecard/sdd-new-phase.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.00137 | $0.02941 |
| Opus 5 | $0.00068 | $0.01470 |
| Sonnet 5 | $0.00027 | $0.00588 |
| Haiku 4.5 | $0.00014 | $0.00294 |
Grade A, and why
sdd-new-phase 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdd-new-phase — add a new active phase to the roadmap
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 adds a fresh active phase — a shippable, independently reviewable, testable vertical slice of work — to specs/roadmap.md as a new ## Phase N — Title block. After writing the edit it invokes the built-in /review skill against the pending change, then stops. Branching, committing, and opening a PR are user actions. Once the roadmap change is merged, /sdd-new-spec <N> materializes the phase into a feature spec.
Inputs
Argument in $ARGUMENTS (optional):
- empty → prompt the user for a one-sentence description of the phase
- short title or one-sentence intent → used as the starting point for title + goal derivation
Hard constraints
- Roadmap-only — zero code changes, zero git actions. This skill never modifies anything outside
specs/roadmap.md. It does not rungit,gh, or any commit / branch / push / PR commands. The user handles git themselves after reviewing the edit. - Do not renumber existing phases. Phase numbers are stable identifiers; completed phases stay in the file with a
✅marker on their heading (per the lifecycle rule inspecs/roadmap.md). The new phase number is alwaysmax(all existing phase numbers) + 1— count both active and ✅-completed phases. - Do not create a feature spec. That is
/sdd-new-spec's job. - Do not touch the
## Later Phases (Not Yet Planned)section or the trailing<!-- Only include items here if they are clearly out of current scope. -->comment. Active phases and the parking lot are distinct. - Do not write to disk before AskUserQuestion completes. The structured questions lock in decisions that shape the entry; writing early wastes the call.
- Ground the phase against
specs/mission.mdandspecs/tech-stack.md. If the proposal obviously conflicts with the constitution (outside mission scope, violates a tech-stack invariant), stop and surface the conflict before asking the user to lock decisions. Depends on:must reference real active phases. If the user names a dependency, it must match a current## Phase N — Titleinspecs/roadmap.md(case-insensitive contains match is fine). Typos get corrected; invented names get rejected.
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 · 143 lines · 137 tokens per session scan A 93ec754d556b
sdd-new-phase is a skill published in the GitHub repository jentic/jentic-api-scorecard (21 stars, last pushed today), licensed Apache-2.0. It adds 137 tokens to every session and 2,941 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…