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 verifygit 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/verify)<a href="https://agentmods.dev/skills/bravodev-hub/appointme/verify"><img src="https://agentmods.dev/badge/skills/bravodev-hub/appointme/verify/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/verify"><img src="https://agentmods.dev/badge/skills/bravodev-hub/appointme/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 16 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.00025 | $0.00555 |
| Opus 5.5 | $0.00010 | $0.00222 |
| Sonnet 5.5 | $0.00005 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
verify 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 1mo 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.
All local certs are self-signed — always `curl -k`. What it actually says
Verifying AppointMe changes at runtime
Launch
cd src/AppointMe.Aspire && dotnet run # run in background; needs Docker up
API is reachable on https://localhost:7233 after ~20–30s (poll GET /api/v1/me, returns 200 anonymous).
Frontend (Vite, proxies /api to the backend) on https://localhost:5173. Keycloak on http://localhost:8082.
All local certs are self-signed — always curl -k.
Getting an authenticated cookie session without a browser
Demo mode is enabled in local dev. One curl call signs in and fills a cookie jar:
curl -sk -c jar.txt "https://localhost:7233/api/v1/login/demo" # 302 = success, sets appointme.auth
curl -sk -b jar.txt -c jar.txt https://localhost:7233/api/v1/me # confirm isAuthenticated:true; refreshes XSRF-TOKEN
Antiforgery (CSRF) notes for mutations
Every GET issues XSRF-TOKEN (readable) + appointme.csrf (HttpOnly) cookies. Cookie-authenticated
unsafe methods under /api require header X-XSRF-TOKEN: <XSRF-TOKEN cookie value> or they 400 with
title "Antiforgery Validation Error". Bearer requests are exempt. Tokens are identity-bound — after
login/logout, refresh via any GET before mutating:
TOKEN=$(grep XSRF-TOKEN jar.txt | awk '{print $NF}')
curl -sk -b jar.txt -H "X-XSRF-TOKEN: $TOKEN" -X POST https://localhost:7233/api/v1/<route> ...
Useful anonymous surfaces
GET /api/v1/me— anonymous-friendly, cheap liveness + auth-state check.POST /api/v1/signup— anonymous mutation, handy for exercising middleware without login (note: empty{}body returns 500 from the handler itself).POST /api/v1/logout— real authenticated mutation; 302 to Keycloak end-session on success, and it cleans up the demo session.
Gotchas
- Stop the Aspire process when done if it wasn't running before you started.
/admin/jobs(Hangfire) redirects (302) when unauthenticated — not an error.
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.
- 1mo ago First seen · 51 lines · 25 tokens per session scan A 87756dcb13b1
verify is a skill published in the GitHub repository bravodev-hub/appointme (50 stars, last pushed 22d ago), licensed MIT. It adds 25 tokens to every session and 555 once invoked, about $0.0001 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
csharp-dotnet
Use when writing, reviewing, testing, or shipping C# / .NET code — ASP.NET Core APIs (minimal APIs vs controllers), EF Core data access, async correctness, solution layout in .cs/.csproj/.sln. NOT a Java/Spring backend (that is spring-boot), NOT a Node/TypeScript backend (that is nestjs), NOT framework-neutral REST…
dotnet-testing-advanced-tunit-advanced
A guide for advanced TUnit testing in .NET. TUnit is a testing framework; the guide covers tests driven by data, dependency injection, integration tests, retries, time limits, and filtering.
dotnet-testing-advanced-aspire-testing
A guide to testing .NET Aspire distributed applications, which are programs made of several coordinated services. It covers tests that run the real service setup through an AppHost, the project that describes how those services are arranged.
dotnet-testing-advanced-aspnet-integration-testing
Guidance for ASP.NET Core integration tests, which test several web application parts together through HTTP requests and responses.
dotnet-testing-advanced-webapi-integration-testing
Guidance for ASP.NET Core Web API integration tests, including HTTP endpoints and ProblemDetails, a standard format for describing API errors.
api-harness
Use the API harness to drive Agentweaver through its REST API, capture the complete request/response evidence, and emit a normalized agentweaver.persona-judge-verdict/v1 JSON verdict. It is for backend/API end-to-end validation; use the UI or MCP harness for those surfaces.