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 fanchenggang/Davflare --skill hello-sitegit clone --depth 1 https://github.com/fanchenggang/DavflareWrote 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/fanchenggang/davflare/hello-site)<a href="https://agentmods.dev/skills/fanchenggang/davflare/hello-site"><img src="https://agentmods.dev/badge/skills/fanchenggang/davflare/hello-site/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/fanchenggang/davflare/hello-site"><img src="https://agentmods.dev/badge/skills/fanchenggang/davflare/hello-site.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.00033 | $0.00409 |
| Opus 5.5 | $0.00013 | $0.00164 |
| Sonnet 5.5 | $0.00007 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
hello-site 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 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.
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
Hello site (reproducible)
Goal: from Cursor chat, publish this folder so
https://sites.<your-domain>/hello/ serves a real page.
No new APIs — only tools already on /mcp.
Prerequisites
- Davflare deployed;
#/settingsleaves API Key, MCP, Sites (and Image host if you want a hero image) on. - Pages env
SITES_HOST= your sites hostname only (e.g.sites.example.com), then redeploy. - Cursor
mcp.jsonpoints athttps://<drive-host>/mcpwith a Bearer API key (see README).
Steps (copy into the agent)
- Read
agents/examples/hello-site/index.htmlfrom this repo (or paste its contents). - Upload it into a drive folder, e.g.
examples/hello-site/index.html(mkdir+upload, encodingutf8). - Call
publish_sitewithslug: "hello"andsource: "examples/hello-site". - Open
https://<SITES_HOST>/hello/— you should see the hello page. - Optional: call
image_uploadwith a small PNG (base64), then edit the HTML to use the returned Markdown / URL andpublish_siteagain.
Do not
- Do not invent new MCP tools.
- Do not put raw API keys in files under
agents/(${env:...}only). - Do not publish to a slug you do not own on a shared demo.
Done when
https://<SITES_HOST>/hello/ returns 200 with the hello markup.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 35 lines · 33 tokens per session scan A 931631f5a33b
hello-site is a skill published in the GitHub repository fanchenggang/Davflare (99 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 409 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-09-05.
Other skills, from other repositories
supermemory
Supermemory is a state-of-the-art memory and context infrastructure for AI agents. Use this skill when building applications that need persistent memory, user personalization, long-term context retention, or semantic search across knowledge bases. It provides Memory API for learned user context, User Profiles for…
files-sdk
Use files-sdk to add file storage to a TypeScript/JavaScript app with a unified API across 49 adapters (S3, R2, GCS, Azure, Vercel Blob, the local filesystem, and more). Triggers when the user wants to upload/download/list/search/move/delete/copy files, generate presigned URLs, do multipart or resumable uploads, range…
prepare-cloudflare-production-deployment
Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment. Use when setting up or auditing Cloudflare MCP resources, wrangler.jsonc bindings, Worker secrets, Turnstile, Email Sending, GitHub Actions secrets/variables, or GitHub CLI deployment wiring for this…
cloudflare
Use when working on Cloudflare's edge platform — wrangler.jsonc bindings, choosing between D1/KV/R2/Durable Objects/Queues, deploying a Worker or SPA via Static Assets, or designing around a Workers runtime limit. NOT generic CI/release (that is deployment), NOT Next.js framework wiring (that is nextjs), NOT DNS…
moemail
Use when an AI agent needs a temporary/disposable email address — for receiving verification emails, testing email integrations, or any task requiring a temporary inbox via the moemail CLI.
review-stack
Stack review of one or more third-party tools (OXC, TanStack, Vite, cf, Sentry, pnpm, Claude Code...) against current official best practices, or of what a dependency bump brings (bumped): one parallel subagent per tool, verified findings, one consolidated plan in chat. USE WHEN: user runs /review-stack or explicitly…