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 bravodev-hub/appointme --skill regenerate-apigit clone --depth 1 https://github.com/bravodev-hub/appointmeWrote 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/bravodev-hub/appointme/regenerate-api)<a href="https://agentmods.dev/skills/bravodev-hub/appointme/regenerate-api"><img src="https://agentmods.dev/badge/skills/bravodev-hub/appointme/regenerate-api/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/bravodev-hub/appointme/regenerate-api"><img src="https://agentmods.dev/badge/skills/bravodev-hub/appointme/regenerate-api.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
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 →
- high Tool Misuse · line 40 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.
- medium Tool Misuse · line 27 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Tool Misuse · line 105 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium MCP Rug Pull · line 93 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00136 | $0.01393 |
| Opus 5.5 | $0.00054 | $0.00557 |
| Sonnet 5.5 | $0.00027 | $0.00279 |
| Haiku 4.5 | $0.00014 | $0.00139 |
Grade A, and why
regenerate-api scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -k -s -o /dev/null -w "%{http_code}" https://localhost:7233/openapi/v1.json How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
regenerate-api
Regenerate src/AppointMe.Frontend/src/api/client.ts and client.schemas.ts from the live backend OpenAPI document. The frontend uses orval with clean: true, so the generated files are fully overwritten on each run.
When to use
Invoke this skill after any change that alters the OpenAPI contract:
- New / renamed / removed endpoint (
*Endpoint.cs, anything implementingIEndpoint) - Changed request or response shape (
*Request.cs,*Response.cs, DTOs) - Changed route, HTTP verb, status codes, or auth attributes on an endpoint
- Changes to value objects exposed through DTOs (e.g.
PersonName,Email) - Permission attribute changes that affect the generated metadata
Do not invoke it for backend-only changes that don't touch the contract (internal handlers, domain events, EF config, migrations, tests).
Preconditions
- Aspire (or at least the
AppointMe.Apiproject) must be running and serving the new code. - The OpenAPI endpoint is
https://localhost:7233/openapi/v1.json(self-signed cert, that's expected). npmis available insrc/AppointMe.Frontend/. This project is npm-based (package-lock.json, noyarn.lock) — never invokeyarnhere, it would write a competing lockfile.
The orval script in package.json sets NODE_TLS_REJECT_UNAUTHORIZED=0 for the self-signed cert — don't add -k flags anywhere else.
Procedure
Run these steps in order. Do not skip the readiness check — running orval against a stale backend silently produces a stale client.
1. Verify the backend is up and serving fresh code
The backend must be restarted after the contract change for orval to see it. Aspire's default project setup does not hot-reload new endpoint signatures.
Check reachability:
curl -k -s -o /dev/null -w "%{http_code}" https://localhost:7233/openapi/v1.json
Interpret:
200— backend is reachable. Continue, but verify with the user that they restarted the API since the contract change (or restart it yourself if you own the terminal). A reachable-but-stale backend is the #1 cause of confusing diffs from this skill.000/ connection refused — backend is not running. Stop and ask the user to start (or restart) Aspire:
Or, if Aspire is already running, restart thecd src/AppointMe.Aspire && dotnet runappointme-apiresource from the Aspire dashboard.
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.
- 2d ago Changed f363e23b233b
- 1mo ago First seen · 111 lines · 136 tokens per session scan A d1ae8b6853c9
regenerate-api is a skill published in the GitHub repository bravodev-hub/appointme (50 stars, last pushed 2d ago), licensed MIT. It adds 136 tokens to every session and 1,393 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
worker-services
Build long-running .NET background services with BackgroundService, Generic Host, graceful shutdown, configuration, logging, and deployment patterns suited to workers and daemons. USE FOR: background services; scheduled workers; hosted services; worker extraction; graceful shutdown, health checks, and service hosting…
aspnet-core
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET. USE FOR: working on ASP.NET Core apps, services, or middleware; changing auth, routing, configuration, hosting, or deployment behavior; deciding…
minimal-apis
Design and implement Minimal APIs in ASP.NET Core using handler-first endpoints, route groups, filters, and lightweight composition suited to modern .NET services. USE FOR: building new HTTP APIs in ASP.NET Core; creating lightweight microservices; choosing between Minimal APIs and controllers. DO NOT USE FOR…
web-api
Build or maintain controller-based ASP.NET Core APIs when the project needs controller conventions, advanced model binding, validation extensions, OData, JsonPatch, or existing API patterns. USE FOR: working on controller-based APIs in ASP.NET Core; needing controller-specific extensibility or conventions; migrating…
managedcode-communication
Use ManagedCode.Communication when a .NET application needs explicit result objects, structured errors, and predictable service or API boundaries instead of exception-driven control flow. USE FOR: integrating ManagedCode.Communication into services or APIs; replacing exception-driven result handling with explicit…
grpc
Build or review gRPC services and clients in .NET. USE FOR: ASP.NET Core gRPC, protobuf contracts, unary or streaming RPC, gRPC client factory, interceptors, deadlines, cancellation, channel reuse, backend service integration. DO NOT USE FOR: broad browser-facing APIs without gRPC-Web tradeoff review, SignalR realtime…