Borrowing it
Nothing to install: this file belongs to ProjectSidewalk/SidewalkWebpage. 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/ProjectSidewalk/SidewalkWebpage/develop/.claude/skills/update-apis/SKILL.mdgit clone --depth 1 https://github.com/ProjectSidewalk/SidewalkWebpageWrote 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/projectsidewalk/sidewalkwebpage/update-apis)<a href="https://agentmods.dev/skills/projectsidewalk/sidewalkwebpage/update-apis"><img src="https://agentmods.dev/badge/skills/projectsidewalk/sidewalkwebpage/update-apis/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/projectsidewalk/sidewalkwebpage/update-apis"><img src="https://agentmods.dev/badge/skills/projectsidewalk/sidewalkwebpage/update-apis.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.00017 | $0.00333 |
| Opus 5.5 | $0.00007 | $0.00133 |
| Sonnet 5.5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
update-apis 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 23d 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
Read docs/architecture.md → "The public API (/v3)" first: it holds the naming contract (camelCase parameters,
snake_case output everywhere except Shapefile), the DTO layout in app/models/api/, and the StreamingApiType
serialization shape. .claude/rules/api.md is the short version.
The set of updates that are likely to be involved:
- Updating the database queries to incorporate the new/updated data (in the
app/models/files). The DTO definitions themselves belong inapp/models/api/*ApiModels.scala, not in the*Table.scalathat produces them. - Making sure the API is updated for every output file type it serves (JSON, CSV, GeoJSON, Shapefile, GeoPackage),
with the serialization on the DTO (
toJson/toCsvRow,csvHeaderin the companion). - Updating the relevant documentation in the
app/views/apiDocs/files and the matchingfrontend/js/api-docs/*Preview.js. - Updating or adding the functional spec in
test/controllers/api/.
A few things to keep in mind:
- Combine common code where it makes sense to do so; reuse
ApiModelUtilsrather than re-rolling CSV/GeoJSON logic. - Run the queries both before and after your updates to check for any regressions.
- v3 is a preview surface: breaking changes are made in place rather than minting a new version.
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.
- 23d ago Changed e05f78a05bf0
- 1mo ago Changed · +8 lines 9534c90ccdc6
- 2mo ago First seen · 14 lines · 17 tokens per session scan A 0a0038aaa58c
update-apis is a skill published in the GitHub repository ProjectSidewalk/SidewalkWebpage (111 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 333 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
agent-desktop-ffi
C-ABI bindings over agent-desktop's PlatformAdapter. Consumers (Python ctypes, Swift, Node ffi-napi, Go cgo, C++, Ruby fiddle) link libagentdesktopffi.{dylib,so,dll} and call ad functions directly instead of spawning the CLI binary per call. The canonical observe-act workflow is: adinit → adadaptercreate[withsession]…
api-security-scan
Review a REST/HTTP API — from its OpenAPI spec or route code — for security gaps like missing auth, broken object-level authorization, no rate limiting, and verbose errors. Reports file:line. Pure Claude Code, no signup.
api-security
OWASP API Security Top 10 (2023) with production Next.js App Router code — access control, authentication, input validation, rate limiting, security headers, data exposure, supply chain, SSRF, and AI tools on those APIs.
api-contracts
API design and contract engineering — REST resource modelling, error envelopes, pagination, filtering, idempotency, versioning and deprecation, rate limiting, webhooks, OpenAPI, GraphQL schema and N+1 defence, and contract testing. Use when designing, reviewing or documenting an endpoint or integration; when the user…
performance-engineering
Performance engineering across the stack — Core Web Vitals (LCP, INP, CLS), bundle size and rendering strategy, image and font optimisation, backend latency budgets, caching layers, database query cost, profiling, and load testing. Use when the user says "slow", "performance", "optimize", "Core Web Vitals", "LCP"…
fastify-best-practices
This skill should be used when working on any Fastify project or when the user asks about Fastify best practices, conventions, or patterns. Trigger when: working on a Fastify project, creating Fastify plugins, registering routes, using decorators, organizing Fastify application structure, using @fastify/autoload…