verify

verify is a skill for Claude Code, Codex from bravodev-hub/appointme. It costs 25 tokens per session (555 once invoked), scanned A, original, MIT.

A procedure for checking AppointMe changes by running its backend, frontend, login flow, and authenticated API requests.

In plain words
What is it for?
Launching the local AppointMe stack, checking its API and frontend, signing in through demo mode, and testing protected changes with the required anti-forgery token.
Why use it?
It catches problems that are not visible from code inspection alone, including login, proxying, cookies, and request-protection failures.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/bravodev-hub/appointme/verify
Any agent
npx skills add bravodev-hub/appointme --skill verify
Clone the repo
git clone --depth 1 https://github.com/bravodev-hub/appointme

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for verify

README.md
[![agentmods](https://agentmods.dev/badge/skills/bravodev-hub/appointme/verify.svg)](https://agentmods.dev/skills/bravodev-hub/appointme/verify)
Your own site
<a href="https://agentmods.dev/skills/bravodev-hub/appointme/verify"><img src="https://agentmods.dev/badge/skills/bravodev-hub/appointme/verify.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 555 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.00555
Opus 5 $0.00013 $0.00278
Sonnet 5 $0.00005 $0.00111
Haiku 4.5 $0.00003 $0.00056

Measured 4d ago against content hash 87756dcb13b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 4d 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`.
.claude/skills/verify/SKILL.md · 51 lines

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.

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.
Changes

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.

  1. 4d ago First seen · 51 lines · 25 tokens per session scan A 87756dcb13b1

Subscribe to this mod's changes

verify is a skill published in the GitHub repository bravodev-hub/appointme (45 stars, last pushed 10d ago), licensed MIT. It adds 25 tokens to every session and 555 once invoked, about $0.0001 per session on Opus 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.